Re: limits.h in gcc 4.3.1 breaks uclibc compilation

2008-08-16 Thread Andrew Pinski
On Sat, Aug 16, 2008 at 5:52 PM, Cristi Magherusan <[EMAIL PROTECTED]> wrote: > Okay, That workaround is really working ;) but is this a good fix on the > long run? Why wouldn't gcc just let those include files where they > belong? limits.h is fixed up header so it belongs in include-fixed. -- Pi

Re: limits.h in gcc 4.3.1 breaks uclibc compilation

2008-08-16 Thread Cristi Magherusan
Hello, On Sat, 2008-08-16 at 21:32 +0300, Cristi Magherusan wrote: > On Sat, 2008-08-16 at 18:21 +, Joseph S. Myers wrote: > > On Sat, 16 Aug 2008, Cristi Magherusan wrote: > > > > > Hello, > > > > > > It seems that gcc-4.3.1 has limits.h in the include-fixed directory, > > > instead of the

Re: [PATCH][RFT] Optimization pass-pipeline re-organization [3/n]

2008-08-16 Thread Richard Guenther
On Fri, 15 Aug 2008, Richard Guenther wrote: > > This is the third patch in the series of optimizing the pass-pipeline, > it applies on top of [1/n]. Cross-posted again to hint people to test > this on their favorite apps. > > Like moving CCP before the initial alias computation is beneficial t

Re: limits.h in gcc 4.3.1 breaks uclibc compilation

2008-08-16 Thread Cristi Magherusan
On Sat, 2008-08-16 at 18:21 +, Joseph S. Myers wrote: > On Sat, 16 Aug 2008, Cristi Magherusan wrote: > > > Hello, > > > > It seems that gcc-4.3.1 has limits.h in the include-fixed directory, > > instead of the include one. > > This breaks uclibc compilation. > > What could be done to fix th

Re: limits.h in gcc 4.3.1 breaks uclibc compilation

2008-08-16 Thread Joseph S. Myers
On Sat, 16 Aug 2008, Cristi Magherusan wrote: > Hello, > > It seems that gcc-4.3.1 has limits.h in the include-fixed directory, > instead of the include one. > This breaks uclibc compilation. > What could be done to fix this? Use uClibc trunk revision 22067 or later. -- Joseph S. Myers [EMAIL

limits.h in gcc 4.3.1 breaks uclibc compilation

2008-08-16 Thread Cristi Magherusan
Hello, It seems that gcc-4.3.1 has limits.h in the include-fixed directory, instead of the include one. This breaks uclibc compilation. What could be done to fix this? Best regards, Cristi. -- Ing. Cristi Măgherușan, Universitatea Tehnică din Cluj-Napoca Centrul de Comunicații "Pusztai Kalman

Re: [PATCH] caret diagnostics

2008-08-16 Thread Paolo Bonzini
I don't know why it was considered bad (and had thought it was simply never reviewed), but I am happy to review such patches as i18n maintainer (including in Stage 3 - they are clearly bug fixes) if the front-end maintainers don't reject them. However, I think they would need splitting up fo

Re: [PATCH] caret diagnostics

2008-08-16 Thread Joseph S. Myers
On Sat, 16 Aug 2008, Paolo Bonzini wrote: > Chris Lattner wrote: > > Please don't forget C++. > > C++ is a completely lost battle. I had a patch to handle all the %s in the > source base, but my approach (which basically implied adding translatable > strings for "a class", "to a class", "with a

Re: Please, do not use the merged revisions log as the commit message when merging

2008-08-16 Thread Manuel López-Ibáñez
2008/8/16 Christopher Faylor <[EMAIL PROTECTED]>: > On Sat, Aug 16, 2008 at 02:35:08PM +0200, Manuel L?pez-Ib??ez wrote: >>Dear GCC devs, >> >>Please do *not* use the full logs of the merged revisions as the >>commit message of a merge. Apart from making the output of svn log >>useless, commits mes

Re: Please, do not use the merged revisions log as the commit message when merging

2008-08-16 Thread Christopher Faylor
On Sat, Aug 16, 2008 at 02:35:08PM +0200, Manuel L?pez-Ib??ez wrote: >Dear GCC devs, > >Please do *not* use the full logs of the merged revisions as the >commit message of a merge. Apart from making the output of svn log >useless, commits messages are parsed are tracked for PR numbers, the >commit

Please, do not use the merged revisions log as the commit message when merging

2008-08-16 Thread Manuel López-Ibáñez
Dear GCC devs, Please do *not* use the full logs of the merged revisions as the commit message of a merge. Apart from making the output of svn log useless, commits messages are parsed are tracked for PR numbers, the commit message is added to the bugzilla page of the PR and people subscribed to th

Re: [PATCH] caret diagnostics

2008-08-16 Thread Paolo Bonzini
Chris Lattner wrote: On Aug 14, 2008, at 8:47 AM, Joseph S. Myers wrote: On Thu, 14 Aug 2008, Robert Dewar wrote: BTW, I am all in favor of caret output, it's not the default in gnat, the default is more like the C default, but -gnatv gives output like: And I'd hope we could keep things th

Re: [PATCH] caret diagnostics

2008-08-16 Thread Robert Dewar
Gabriel Dos Reis wrote: I'm in favor of getting -fdiagnostics-show-caret=no by default in this release, and enable people like you to get useful stuff done. That gives us time to iron out outstanding bugs for the next release (and making it the default). That's a good idea regardless of the ev

Re: [PATCH] caret diagnostics

2008-08-16 Thread Robert Dewar
Gabriel Dos Reis wrote: On Thu, Aug 14, 2008 at 11:52 AM, Tom Tromey <[EMAIL PROTECTED]> wrote: "Joseph" == Joseph S Myers <[EMAIL PROTECTED]> writes: I'd like to see carets on by default as part of a major release -- say GCC 5.0. (First mention!!) 100% agreed. -- Gaby As I have mention