Dan Nicholson wrote:
> On 10/31/07, Brian Paul <[EMAIL PROTECTED]> wrote:
>> Dan Nicholson wrote:
>>> Hi Brian,
>>>
>>> It seems most distros are building Mesa with the GCC option
>>> -fno-strict-aliasing. Here were a couple bugs I could find that this
>>> works around:
>>>
>>> https://bugs.freedesktop.org/show_bug.cgi?id=6046
>>> http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=394311
>>>
>>> Should this be in Mesa by default for the GCC targets?
>> If that'll work around some bugs then I'm OK with that for the short term.
>>
>> Longer term, maybe we can trying fixing the code.  It looks like
>> -Wstrict-aliasing=2 -fstrict-aliasing should give some indications of
>> problem areas.
> 
> That's pretty much what I was thinking. Obviously, it's better to fix
> the code, so maybe it's better to just let the distros add it for
> their "production" builds and let it be off by default for the
> developers. On the other hand, adding it with a comment about why
> might be helpful:
> 
> # Work around aliasing bugs - this should be off for development
> CFLAGS += -fno-strict-aliasing

Go ahead and do that.


> Is there a BUGS or TODO file of some sort? That would certainly be
> something to note and would give new developers something to chew on.
> Maybe docs/todo.html?

There's a help-wanted file, but probably pretty out of date.  I'll see 
about updating it a bit...

-Brian

-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Mesa3d-dev mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to