Le 5 sept. 2012 à 20:12, Peter Grehan a écrit :
> Another system:
>
> CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (3392.36-MHz K8-class CPU)
> Origin = "GenuineIntel" Id = 0x306a9 Family = 6 Model = 3a Stepping = 9
> Features=0xbfebfbff
> Features2=0x7fbae3ff
> AMD Features=0x28100800
> A
On Wed, Sep 05, 2012 at 11:31:26AM +0200, Dimitry Andric wrote:
> On 2012-09-05 01:40, Garrett Cooper wrote:
> ...
> > Steve does have a point. Posting the results of
> >CFLAGS/CPPFLAGS/LDFLAGS/etc for config.log (and maybe poking through
> >the code to figure out what *FLAGS were used elsewher
On Wed Sep 5 12, Eir Nym wrote:
> I've got following warnings [no errors had been generated while
> -Werror is in command line] and want to know if they are ok. There are
> much more same warnings in modules, but I worry about kernel :
> Kernel config: http://eroese.org/_/_/pub/bsd/240070/GENERIC_
On 2012-09-05 19:59, Eir Nym wrote:
I've got following warnings [no errors had been generated while
-Werror is in command line] and want to know if they are ok.
Most of these warnings are harmless, and just point out that the
compiler will optimize unused code away, such as tests that always
su
Another system:
CPU: Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz (3392.36-MHz K8-class CPU)
Origin = "GenuineIntel" Id = 0x306a9 Family = 6 Model = 3a
Stepping = 9
Features=0xbfebfbff
Features2=0x7fbae3ff
AMD Features=0x28100800
AMD Features2=0x1
TSC: P-state invariant, performance sta
I've got following warnings [no errors had been generated while
-Werror is in command line] and want to know if they are ok. There are
much more same warnings in modules, but I worry about kernel :
Kernel config: http://eroese.org/_/_/pub/bsd/240070/GENERIC_PF.amd64
src.conf: http://eroese.org/_/_/
I've been compiling clang with itself on PPC64 for a while now. Works quite
good :)
On Wed, Sep 05, 2012 at 01:44:00PM -0400, Justin Hibbits wrote:
> Actually, Nathan does say it's gcc's fault in a comment on that bug.
> However, I do all my clang work compiling it with gcc4.2.1, so run into
> th
Actually, Nathan does say it's gcc's fault in a comment on that bug.
However, I do all my clang work compiling it with gcc4.2.1, so run into
this constantly when I forget to add the flag.
- Justin
On Wed, Sep 5, 2012 at 1:37 PM, Roman Divacky wrote:
> What makes you think it's a bug in llvm co
What makes you think it's a bug in llvm code and not a plain gcc miscompile?
Other people seem to compile llvm on PPC64 with gcc and -fstrict-aliasing
just fine. They just dont happen to use gcc4.2.1. Ie. gcc47 is reported
to not have this problem. I personally can confirm that fbsd+gcc48 is ok to
On 2012-09-05 15:27, David Wolfskill wrote:
...
/usr/src/sys/dev/hpt27xx/osm_bsd.c:1180:25: error: format string is not a
string literal (potentially insecure) [-Werror,-Wformat-security]
S_IRUSR | S_IWUSR, driver_name);
^~~
Thanks, fixed in
On 05-09-2012 16:11, O. Hartmann wrote:
> Hello.
>
> While fiddling around with software that is looking for an include file
> "atomic_ops.h", which seems to reside in the FreeBSD operating system's
> sources with lib/lbkse, I'd like to know whether those architecture
> specific header files are i
On Wed, 2012-09-05 at 16:11 +0200, O. Hartmann wrote:
> Hello.
>
> While fiddling around with software that is looking for an include file
> "atomic_ops.h", which seems to reside in the FreeBSD operating system's
> sources with lib/lbkse, I'd like to know whether those architecture
> specific head
Hello.
While fiddling around with software that is looking for an include file
"atomic_ops.h", which seems to reside in the FreeBSD operating system's
sources with lib/lbkse, I'd like to know whether those architecture
specific header files are installed in some places, where they could be
found b
Running:
FreeBSD g1-227.catwhisker.org 10.0-CURRENT FreeBSD 10.0-CURRENT #669 240081M:
Tue Sep 4 05:02:11 PDT 2012
r...@g1-227.catwhisker.org:/usr/obj/usr/src/sys/CANARY i386
After updating sources to r240131, I see:
...
>>> stage 3.2: building everything
...
clang -c -O -pipe -std=c99
On Wed, Sep 5, 2012 at 6:56 AM, Dimitry Andric wrote:
> On 2012-09-05 11:36, David Chisnall wrote:
>
>> On 5 Sep 2012, at 10:31, Dimitry Andric wrote:
>>
>>>TThe
>>>
>>>-fno-strict-aliasing is not really my choice, but it was introduced
>>>in the past by Nathan Whitehorn, who apparent
On 2012-09-05 11:36, David Chisnall wrote:
On 5 Sep 2012, at 10:31, Dimitry Andric wrote:
TThe
-fno-strict-aliasing is not really my choice, but it was introduced
in the past by Nathan Whitehorn, who apparently saw problems without
it. It will hopefully disappear in the future.
Cla
On 5 Sep 2012, at 10:31, Dimitry Andric wrote:
> These are just the default FreeBSD optimization flags for building
> clang, which are probably used by the majority of users out there.
> This is the case that I was interested in particularly. The
> -fno-strict-aliasing is not really my ch
On 2012-09-05 01:40, Garrett Cooper wrote:
...
Steve does have a point. Posting the results of
CFLAGS/CPPFLAGS/LDFLAGS/etc for config.log (and maybe poking through
the code to figure out what *FLAGS were used elsewhere) is more
valuable than the data is in its current state (unfortunately..
On 2012-09-05 10:11, O. Hartmann wrote:
Udating/reinstalling of both ports www/firefox (15.0) and
mail/thunderbird (15) fail with an error like showed below.
./jsproxy.h:17:7: error: visibility does not match previous declaration
class JS_FRIEND_API(BaseProxyHandler) {
Please see: http:/
Hello.
Udating/reinstalling of both ports www/firefox (15.0) and
mail/thunderbird (15) fail with an error like showed below.
Last time I saw this on FreeBSD 10.0-CUR ( r240108M), it was almost the
same issue due to the compiler change from CLANG 3.0 -> 3.1 as far as I
experienced and has been fix
On Wed, Sep 05, 2012 at 09:33:55AM +0200, Fabien Thomas wrote:
> >
> > Hi,
> >
> > here are the results
> >
> > # pmccontrol -L
> > SOFT
> >CLOCK.STAT
> >CLOCK.HARD
> >LOCK.FAILED
> >PAGE_FAULT.WRITE
> >PAGE_FAULT.READ
> >PAGE_FAULT.ALL
> >
> Seem
>
> Hi,
>
> here are the results
>
> # pmccontrol -L
> SOFT
>CLOCK.STAT
>CLOCK.HARD
>LOCK.FAILED
>PAGE_FAULT.WRITE
>PAGE_FAULT.READ
>PAGE_FAULT.ALL
>
Seems that the CPU was not detected can you dump the dmesg with CPU: section ?
As Davide ask, if
on 04/09/2012 19:01 Ryan Stone said the following:
> I have a Intel Sandy Bridge system that reports that it has SMT cores
> instead of HTT(under a derivative of FreeBSD 8.2). I'll admit that I
> don't at all understand the distinction between the two -- I thought
> that HTT was just Intel's name
23 matches
Mail list logo