Snapshot gcc-4.4-20090109 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.4-20090109/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.4 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
Bernd Roesch wrote:
> Hello Andy
>
> On 07.01.09, you wrote:
>
>
>> Cygwin one:
>>
>> When it gets to stage 3 (after many hours) I get the following printed
>> out to the console (not redirected) -
>>
>> 217 [unknown (0x1B0)] conftest 3408 _cygtls::handle_exceptions: Error
>> while dumping state (p
On Fri, Jan 9, 2009 at 4:59 PM, Ian Lance Taylor wrote:
> "Richard Guenther" writes:
>
>> On Fri, Jan 9, 2009 at 4:31 PM, Ian Lance Taylor wrote:
>>> "Richard Guenther" writes:
>>>
> There are many ways to align data without exposing it in the
> ABI--e.g., the alignment of a global arra
"Richard Guenther" writes:
> On Fri, Jan 9, 2009 at 4:31 PM, Ian Lance Taylor wrote:
>> "Richard Guenther" writes:
>>
There are many ways to align data without exposing it in the
ABI--e.g., the alignment of a global array is not part of the ABI, in
that nothing breaks if the alig
"H.J. Lu" writes:
> You can't use _attribute__ ((aligned(max))) directly with memory
> allocator. How about a new macro, __BIGGEST_ALIGNMENT__?
You can use __attribute__ ((aligned)), you just need to also use
__alignof__. I have no objection to __BIGGEST_ALIGMENT__ but that is
a separate discus
On Fri, Jan 9, 2009 at 4:31 PM, Ian Lance Taylor wrote:
> "Richard Guenther" writes:
>
>>> There are many ways to align data without exposing it in the
>>> ABI--e.g., the alignment of a global array is not part of the ABI, in
>>> that nothing breaks if the alignment is increased. Also, there are
"Richard Guenther" writes:
>> There are many ways to align data without exposing it in the
>> ABI--e.g., the alignment of a global array is not part of the ABI, in
>> that nothing breaks if the alignment is increased. Also, there are
>> many programs which simply don't care about an external ABI
On Thu, Jan 8, 2009 at 9:41 PM, Ian Lance Taylor wrote:
> "H.J. Lu" writes:
>
>>> There are many ways to align data without exposing it in the
>>> ABI--e.g., the alignment of a global array is not part of the ABI, in
>>> that nothing breaks if the alignment is increased. Also, there are
>>> many
On Thu, Jan 8, 2009 at 7:22 PM, Ian Lance Taylor wrote:
>
> Per Ekman writes:
>
> > Is it possible to get hold of the calling function (in the compiled
> > program, not in gcc itself) in c-typeck.c:build_function_call()?
>
> It's in the global variable current_function_decl.
Perfect, that did th
Seongbae Park ??? ??? wrote:
On Thu, Jan 8, 2009 at 10:11 AM, Hariharan wrote:
Hi Seongbae,
Does that mean that someone cant use the profile just to annotate branches
(and get better code by that), without having to get the additional baggage
of "unroll-loops", "peel-loops" etc?
You can do
On Fri, Jan 9, 2009 at 2:22 AM, Ian Lance Taylor wrote:
> "H.J. Lu" writes:
>
>>> For that matter, don't we have a problem on x86 GNU/Linux, where
>>> malloc returns an 8-byte alignment but attribute((aligned)) is a 16
>>> byte alignment?
>>
>> I don't think it is the same as MALLOC_ABI_ALIGNMENT
11 matches
Mail list logo