On Saturday 06 August 2011 00:52:02 Thomas Koenig wrote:
> Hello world,
>
> I just noticed that C++ now appears to be built by default, even when
> only the C and fortran are specified.
Yes, but it doesn't make much difference in practice. The only difference I
saw is the debugging symbols includ
On 08/06/2011 11:22 AM, Mikael Morin wrote:
WRT to bootstrap time, as usual: it's too long.
Well, that all depends on your (time) frame of reference, of course. In
the summer months leading up to Craig Burley asking for volunteers
testing g77 (the g77-alpha phase), i.e., during the summer o
On 08/04/2011 01:10 PM, Andrew Haley wrote:
>> It's the sort of thing that gets done in threaded interpreters,
>> where you really need to keep a few pointers in registers and
>> the interpreter itself is a very long function. gcc has always
>> done a dreadful job of register allocation in s
On Sat, Aug 06, 2011 at 03:16:43PM +0200, Toon Moene wrote:
> On 08/06/2011 11:22 AM, Mikael Morin wrote:
>
> >WRT to bootstrap time, as usual: it's too long.
>
> Well, that all depends on your (time) frame of reference, of course. In
> the summer months leading up to Craig Burley asking for vo
On Wed, 8 Jun 2011, Andreas Schwab wrote:
Basile Starynkevitch writes:
And I also believe that the minuscule patch I am proposing in
http://gcc.gnu.org/ml/gcc/2011-06/msg00081.html
should work on your system too. Could you try it please?
That's not the point. The point is, if you patch, yo
Ping. AVX2 support depends on this patch.
Thanks.
On Thu, Aug 4, 2011 at 5:49 PM, H.J. Lu wrote:
> On Thu, Aug 4, 2011 at 4:44 PM, H.J. Lu wrote:
>> On Thu, Aug 4, 2011 at 3:46 PM, Joseph S. Myers
>> wrote:
>>> On Thu, 4 Aug 2011, H.J. Lu wrote:
>>>
Here is the updated patch to get prop
On 08/06/2011 05:14 PM, Steve Kargl wrote:
You left out the crucial hardware spec. How much memory
did you have 19 years ago compared to the system today?
My experience with g++ is that it will consume more memory
than gcc.
That might be true - I have never experienced memory shortage *buildi
Hello,
This isn't really a compiler bug, but it's something which the manual
doesn't describe too well so I thought I would point this out.
This page of the manual:
http://gcc.gnu.org/onlinedocs/cpp/Common-Predefined-Macros.html#Common-Predefined-Macros
says this:
"
You should use these macros f
Snapshot gcc-4.7-20110806 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.7-20110806/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
On Sat, Aug 6, 2011 at 5:40 PM, Christopher Huang-Leaver
wrote:
> Output:
>
> small end first
> big end first
>
> gcc -v
> gcc version 4.4.5 (Gentoo 4.4.5 p1.2, pie-0.4.5)
>
I got the same result with g++-4.4 (4.4.6), g++-4.5 (4.5.3) on Debian
testing. But with g++-4.6, I got
small end first
on
On 6 August 2011 22:40, Christopher Huang-Leaver wrote:
> Hello,
>
> This isn't really a compiler bug, but it's something which the manual
> doesn't describe too well so I thought I would point this out.
>
> This page of the manual:
> http://gcc.gnu.org/onlinedocs/cpp/Common-Predefined-Macros.html#
On Sat, Aug 6, 2011 at 9:35 PM, Jonathan Wakely wrote:
> On 6 August 2011 22:40, Christopher Huang-Leaver wrote:
>> Hello,
>>
>> This isn't really a compiler bug, but it's something which the manual
>> doesn't describe too well so I thought I would point this out.
>>
>> This page of the manual:
>>
12 matches
Mail list logo
