In 4.3.2, it seems to me that bootstrap4 does not skip compare, so fails
when it is precisely needed. I did a bootstrap4, compare failed, but manual
make compare3 succeeded.
I guess a workaround is:
/src/configure -disable-bootstrap
make
make install
rm -rf *
/src/configure
What are the rules for porting patches back from the graphite
branch that fix ICEs when -fgraphite is used to compile code?
There doesn't seem to have been much movement of patches out of
the graphite branch lately.
Jack
2008/11/1 Jonathan Wakely:
> 2008/10/28 S. Tang:
>> Hello there,
>>
>> From what I understand, if one uses placement new with a parameter to
>> initialize a class, and if that class' constructor throws an exception, then
>> a matching delete operator is called to release the memory.
>>
>> This do
On Sat, Nov 01, 2008 at 11:14:14AM +, Andrew Haley wrote:
> Jack Howarth wrote:
> > On Fri, Oct 31, 2008 at 02:30:25PM -0700, Andrew Pinski wrote:
> >> I get the following build failure on i386-apple-darwin8.11.1.
> >>
> >>
> >> libtool: link: /Users/apinski/src/local/gcc/objdir/gcc/gcj
> >> -B
2008/10/28 S. Tang <[EMAIL PROTECTED]>:
> Hello there,
>
> From what I understand, if one uses placement new with a parameter to
> initialize a class, and if that class' constructor throws an exception, then
> a matching delete operator is called to release the memory.
>
> This does not seem to w
Angel Tsankov wrote:
> Angel Tsankov wrote:
>> [..] the -I. option seems to be ignored.
>
> A further investigation reveals that GCC ignore not only "-I." but
> also "-I".
>
Still further investigation shows that versions 2.95.4, 3.0.4, and 3.1.1
take into account "-I", while versions
3.2.3 and 4
Status
==
The two months of Stage 3 have ended and the trunk is now in regression
and documentation fixes only mode.
At this point bugfixing should concentrate on getting the list of serious
regressions down to a level that makes GCC 4.4 ready to release.
As an exception to this we will still
Angel Tsankov wrote:
> [..] the -I. option seems to be ignored.
A further investigation reveals that GCC ignore not only "-I." but also
"-I".
Jack Howarth wrote:
> On Fri, Oct 31, 2008 at 02:30:25PM -0700, Andrew Pinski wrote:
>> I get the following build failure on i386-apple-darwin8.11.1.
>>
>>
>> libtool: link: /Users/apinski/src/local/gcc/objdir/gcc/gcj
>> -B/Users/apinski/src/local/gcc/objdir/i386-apple-darwin8.11.1/libjava/
>> -B/U
Angel Tsankov wrote:
> Result on my system:
> dbgcnt.o: ../dbgcnt.c ../include/config.h
>
I meant that on my system the commands produce exactly the same result,
i.e. the -I. option seems to be ignored.
On Sat, Nov 1, 2008 at 8:27 AM, Reza Roboubi <[EMAIL PROTECTED]> wrote:
> I believe gcc treats all function calls as fairly sacred and doesn't really
> optimize across function calls much. For example, the pcre(regex) library
> creates it's own stack frames and "simulates" the entire function recu
Hi,
Here's how the test case:
1. Create the following directory tree:
|--include/config.h (may be empty)
|--source/config.h (may be empty)
\--dbgcnt.c (contains only '#include "config.h"')
2. Go to directory "source" and execute the following commands:
gcc -M -I../include -I. ../dbgcnt.c
gcc
Hi,
I am working on IA64 and gcc4.1.1. My primary work is to use control
speculation on IA64 to implement efficient taint tracking. We have
already had a paper on ISCA'08.
For this purpose, I add a pass (before the 2nd instruction scheduling)
to instrument loads, stores, and compares. During
I believe gcc treats all function calls as fairly sacred and doesn't
really optimize across function calls much. For example, the
pcre(regex) library creates it's own stack frames and "simulates" the
entire function recursion to overcome this (and I think it has to,
otherwise big inefficiencie
14 matches
Mail list logo
