Re: -Warray-bounds false negative

2009-11-13 Thread Matt
On Fri, 13 Nov 2009, Andrew Pinski wrote: On Fri, Nov 13, 2009 at 1:09 PM, Matt wrote: Hello, I recently came across a false negative in GCC's detection of array bounds violation. At first, I thought the other tool (PC-Lint) was having false positive, but it turns out to be correct. The false

Re: -Warray-bounds false negative

2009-11-13 Thread Andrew Pinski
On Fri, Nov 13, 2009 at 1:09 PM, Matt wrote: > Hello, > > I recently came across a false negative in GCC's detection of array bounds > violation. At first, I thought the other tool (PC-Lint) was having false > positive, but it turns out to be correct. The false negative occurs in GCC > 4.3, 4.4.1,

-Warray-bounds false negative

2009-11-13 Thread Matt
Hello, I recently came across a false negative in GCC's detection of array bounds violation. At first, I thought the other tool (PC-Lint) was having false positive, but it turns out to be correct. The false negative occurs in GCC 4.3, 4.4.1, and latest trunk (4.5). I'm curious to understand ho

Re: (C++) mangling vector types

2009-11-13 Thread Mark Mitchell
Gabriel Dos Reis wrote: >> This still seems a lot of complexity to me, and I still think inserting >> a new version between 2 and 3 is odd. If we need the complexity, I >> think we have to introduce a new orthogonal option for vector mangling, >> independent of the ABI version, but implied by ABI

Re: (C++) mangling vector types

2009-11-13 Thread Gabriel Dos Reis
On Thu, Nov 12, 2009 at 5:57 PM, Mark Mitchell wrote: > Jason Merrill wrote: > >> It isn't such a corner case, unfortunately; any code that tries to >> overload on multiple vector sizes (i.e. MMX and SSE vectors) will break. >>  See bug 12909 and its duplicates.  This is becoming more of a problem

Re: more graphite merges before gcc 4.5 branch?

2009-11-13 Thread Jack Howarth
On Thu, Nov 12, 2009 at 01:23:30PM -0500, David Edelsohn wrote: > > Yes, more Graphite merges are planned. The VTA merge broke Graphite > and we are waiting for Alexandre's recent VTA fixes for Graphite to be > updated based on the initial feedback from Sebastian and merged into > the trunk. The

Re: i370 port - constructing compile script

2009-11-13 Thread Ulrich Weigand
Paul Edwards wrote: > The thing is, I already know it has detected that I don't have > strcasecmp. That's why it doesn't have HAVE_STRCASECMP > defined in the config.h. You are right that I don't have a linker, > but the compile with error-on-no-prototype is working fine - I > can see the result

Re: i370 port - constructing compile script

2009-11-13 Thread Paul Edwards
Next, a stack of libiberty files were not compiled - strcasecmp, vasprintf, asprintf, getpagesize, strdup. I don't know why this would be the case, because e.g. HAVE_STRCASECMP is not defined. Anyway, I added them to the source list manually, and with a script, awk and m4, I was able to produce

Re: i370 port - constructing compile script

2009-11-13 Thread Ulrich Weigand
Paul Edwards: > 1. I think my unixio.h, which has a stack of POSIX functions > that need to be there (mkdir, pwait, open, fileno etc), needs to > be considered "honorary ansi" (after all, so much code assumes > that they exist) and get included in ansidecl, with unixio.h > living in include, and u

Re: i370 port - constructing compile script

2009-11-13 Thread Ulrich Weigand
Paul Edwards wrote: > First of all, I got link errors, because sched-ebb etc were trying > to call various functions, but those functions were not being > compiled in because INSN_SCHEDULING was not defined > (that's my quick analysis, anyway). So I just grepped those > files out of the "source l

Re: i370 port - constructing compile script

2009-11-13 Thread Paul Edwards
Ok, now I have some results from the auto-compile-script-generation. I got it to work, but it required some manual corrections. First of all, I got link errors, because sched-ebb etc were trying to call various functions, but those functions were not being compiled in because INSN_SCHEDULING was