Default -fabi-version=0 for 4.9

2013-03-04 Thread Jason Merrill
Our policy on mangling bugs has been that we don't change the mangling unless users explicitly specify -fabi-version. Over time, this means that quite a few bugs have been found but continue to accumulate. Most of these are C++11-specific, which means that as users use C++11 more frequently,

C++ conversion: an observation about minimum compiler version

2013-03-04 Thread Thierry Moreau
Hi, This is just an observation, but maybe there is a potential problem. I am a happy user of GCC and I have many 4.x versions that I use on three development Linux boxes. The C++ template code in annex triggers a compile-time error on 4.2, 4.4, 4.6, but not on 4.7. (I suppose this bug has be

Re: Default -fabi-version=0 for 4.9

2013-03-04 Thread Jeff Law
On 03/04/2013 11:31 AM, Jason Merrill wrote: Our policy on mangling bugs has been that we don't change the mangling unless users explicitly specify -fabi-version. Over time, this means that quite a few bugs have been found but continue to accumulate. Most of these are C++11-specific, which mean

Re: Default -fabi-version=0 for 4.9

2013-03-04 Thread Jason Merrill
On 03/04/2013 03:46 PM, Jeff Law wrote: Seems reasonable. Presumably -Wabi will warn folks if they're doing something that results in a different mangling? Currently -Wabi warns about things that will are different in a later version; it would probably make sense to allow people to write some

Re: C++ conversion: an observation about minimum compiler version

2013-03-04 Thread Jonathan Wakely
On 4 March 2013 19:59, Thierry Moreau wrote: > > The observation is *if* the gcc source code has some C++ depency(ies) which > similarly needs say version>=4.7 and a machine has only gcc 4.4 installed, > then migrating to e.g. gcc 5.3 requires installing v.X, (4.7 <= X < > first-version-that-can't-

Suppress warning for conversion prototype (that is present) (Bug 6144)

2013-03-04 Thread Jeffrey Walton
Hi All, I'm working on Apple, so I'm stuck with some ancient stuff. I'm trying to compile with -Wall -Wextra -Wconversion, and I'm catching a warning similar to http://gcc.gnu.org/bugzilla/show_bug.cgi?id=38116. The 38116 bug defers to Bug 6144 (http://gcc.gnu.org/bugzilla/show_bug.cgi?id=6614).

Re: Modeling predicate registers with more than one bit

2013-03-04 Thread Hans-Peter Nilsson
On Thu, 28 Feb 2013, Paulo Matos wrote: > Hello, > > I am looking at how to correctly model in GCC predicate > registers that have more than one bit and the value set into to > the predicate register after a comparison depends on the size > of the comparison. > > I have looked into GCC backends but