Redhat branches at git mirror

2011-03-11 Thread Kirill A. Shutemov 
Some of Linux distributions use Redhat branches as base for their builds
of GCC.

It would be nice to have Redhat branches in git mirror. At least for gcc
4.3 - 4.6.

-- 
 Kirill A. Shutemov

Re: New blank line after 'all warnings being treated as errors'

2011-03-11 Thread Richard Guenther 
On Fri, Mar 11, 2011 at 4:41 AM, Diego Novillo  wrote:
> After -Werror is triggered, we are now emitting an extra blank line
> that we were not emitting before.  Was this change intentional?  Does
> anyone recognize this?
>
> $ cat a.cc
> char c = 257;
> $ g++-4.4.3 -c -o /dev/null -Werror a.cc
> cc1plus: warnings being treated as errors
> a.cc:1: error: overflow in implicit constant conversion
> $
>
> But with trunk, I get:
>
> $ ~/gcc-trunk/native/bin/g++ -c -o /dev/null -Werror a.cc
> a.cc:1:10: error: overflow in implicit constant conversion [-Werror=overflow]
> cc1plus: all warnings being treated as errors
> [... extra blank line ...]
> $
>
> It looks odd.  Should we change it back to the old way?  (maybe I just
> missed the documentation on the change).

I think it's a bug.

Richard.

Re: New blank line after 'all warnings being treated as errors'

2011-03-11 Thread Diego Novillo 
On Fri, Mar 11, 2011 at 07:53, Richard Guenther
 wrote:

> I think it's a bug.

OK, thanks for confirming.  I filed
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48071.  Would a fix for
this be OK for 4.6?


Diego.

Re: New blank line after 'all warnings being treated as errors'

2011-03-11 Thread Richard Guenther 
On Fri, Mar 11, 2011 at 3:33 PM, Diego Novillo  wrote:
> On Fri, Mar 11, 2011 at 07:53, Richard Guenther
>  wrote:
>
>> I think it's a bug.
>
> OK, thanks for confirming.  I filed
> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48071.  Would a fix for
> this be OK for 4.6?

Sure, it's a regression.

>
> Diego.
>

Inline param docs up-to-date?

2011-03-11 Thread Benjamin Redelings 

Hi,

I have a C++ numerical code which runs about 40% slower which 
compiled with 4.6 than with 4.5. I plan to submit a bug report later -- 
reducing the bug to a test case will take a while and I can't start yet.


Can anyone tell me if the 4.6 svn manpage is currently up-to-date 
in describing the function and default values of the --param's that 
control inlining?  (I'd like to see changes in inlining behavior could 
be responsible for the slowdown.)


thanks,

-BenRI

Re: Inline param docs up-to-date?

2011-03-11 Thread Richard Guenther 
On Fri, Mar 11, 2011 at 5:00 PM, Benjamin Redelings
 wrote:
> Hi,
>
>    I have a C++ numerical code which runs about 40% slower which compiled
> with 4.6 than with 4.5. I plan to submit a bug report later -- reducing the
> bug to a test case will take a while and I can't start yet.
>
>    Can anyone tell me if the 4.6 svn manpage is currently up-to-date in
> describing the function and default values of the --param's that control
> inlining?  (I'd like to see changes in inlining behavior could be
> responsible for the slowdown.)

They are not up-to-date, you can check gcc/params.def for the current
defaults though.  --help=params should probably try to print the defaults.

Richard.

> thanks,
>
> -BenRI
>