I successfully built and installed GCC 4.0.3 on Slackware 10.2.
Bootstrapping info:
1. Output of srcdir/config.guess:
i686-pc-linux-gnu
2. Output of "gcc -v":
Using built-in specs.
Target: i686-pc-linux-gnu
Configured with: ../gcc-src/gcc-4.0.3/configure
Thread model: posix
gcc version 4.0.3
> You know, I've always wondered why there wasn't a lisp-family front end
> for GCC, the roots of GNU and RMS being where they are (and didn't RMS
> promise way back when to make lisp suitable for unix systems
> programming?). I'm just not connected enough to the lisp world to know
> the answer I
Diego Novillo wrote:
> On 03/30/06 03:32, Adriaan van Os wrote:
>
>> Still, I would like to create a GNU Pascal branch for gcc. This will be
>> a central place where to keep the compiler updated with
>>
> I don't think this is a good idea. You are either part of the compiler
> or you aren't. Fro
Snapshot gcc-4.1-20060331 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.1-20060331/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.1 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches
>
>
> Hello,
>
> I'm trying to build GCC-4.2-20060325 on OpenBSD 3.9-current, but it fails
> with:
>
> echo timestamp > s-gtype
> /home/karel/build/gcc-4.2-20060325/gcc/read-rtl.c:787: warning: missing
> sentinel in function call
This usually means NULL is defined as 0 instead of (void*)0.
PR26763 is
int try (int *a)
{
return a + -1 > a;
}
int main(void)
{
int bla[100];
if (try (bla + 50))
abort ();
return 0;
}
now, this looks like a perfectly valid testcase which pointer_int_sum
makes questionable, because it produces
a + -4B > a
which has an overflowing pointer
"Shaun Jackman" <[EMAIL PROTECTED]> writes:
> GCC reports an error for this snippet:
>
> int main()
> {
> foo:
> int x;
> }
>
> foo.c:4: error: expected expression before 'int'
The C standard only allows labels to occur before statements. A
declaration is not a statement.
Andreas.
--
An
GCC reports an error for this snippet:
int main()
{
foo:
int x;
}
foo.c:4: error: expected expression before 'int'
... but not this snippet:
int main()
{
foo:
(void)0;
int x;
}
Is this expected behaviour? At the very least, it seems like an
unusual distinction.
Please
Hello,
I've checkouted todays sources from trunk and I can confirm that the same
failure also happens there.
Cheers,
Karel
On Fri, 31 Mar 2006, Karel Gardas wrote:
Hello,
I'm trying to build GCC-4.2-20060325 on OpenBSD 3.9-current, but it fails
with:
echo timestamp > s-gtype
/home/kar
On 3/30/06, Adriaan van Os <[EMAIL PROTECTED]> wrote:
> the problem is not regular testing.
Then waht is the problem with the daily maintenance you mention? Maybe
there are other ways to make life easier for the gpc folks if you
would be more specific about the problems you apparently have.
> >
Hi,
I was trying to convert the gcc C-Gimple form to the internal AST
representation used in our research compiler. I was able to transform most
of the nodes of the GIMPLE tree but was not able to find out a way to
retrieve the global declarations from the GIMPLE tree. For example is there
a way t
> > On irc today we were discussing handling 'this' in gcj. We can add an
> > attribute to the argument to mark it as non-null... but strangely
> > there doesn't seem to be a way to mark other local variables as
> > known-non-null -- a curious deficiency.
> It seems to me that for other locals tha
It would take a massive target-specific backend hack to make that
happen, as GCC currently only supports flat address spaces. ;-)
Rémy Saissy wrote:
Hi everybody,
I'm looking for gcc support of x86-32 segment registers but the only information
I've found about it is in this old thread:
http://
On 03/31/06 04:08, Jeffrey A Law wrote:
> Then we just need to make VRP not be so quick to ignore statements
> with virtual operands (ie, the same problem we need to solve if
> VRP is going to be able to use non-null attributes on function
> return values).
>
Certainly. The approach I had sketch
Hello,
I'm trying to build GCC-4.2-20060325 on OpenBSD 3.9-current, but it fails
with:
echo timestamp > s-gtype
/home/karel/build/obj-gcc-4.2-20060325/./prev-gcc/xgcc
-B/home/karel/build/obj-gcc-4.2-20060325/./prev-gcc/
-B/home/karel/usr/local/gcc-4.2-20060325/i386-unknown-openbsd3.9/bin/ -
> Setting TREE_OVERFLOW here sounds like the bug.
Well, it's the standard semantics of the middle-end, nothing more:
/* A subroutine of fold_convert_const handling conversions of an
INTEGER_CST to another integer type. */
static tree
fold_convert_const_int_from_int (tree type, tree arg1)
{
On Fri, 2006-03-31 at 09:55 +0100, Andrew Haley wrote:
> Well, it's not just functionss but also global variables. AFAICS
> there are three sources of data: args, retvals, and globals. And
> there are quite a few of these globals we can usefully tag as "known
> never to be null".
Seems to me the
Jeffrey A Law writes:
> On Thu, 2006-03-30 at 18:39 +0100, Andrew Haley wrote:
> > Jeffrey A Law writes:
> > > On Wed, 2006-03-29 at 14:28 -0700, Tom Tromey wrote:
> > >
> > > > On irc today we were discussing handling 'this' in gcj. We can add an
> > > > attribute to the argument to ma
Adriaan van Os <[EMAIL PROTECTED]> wrote:
>> and people are
>> responsible for fixing all front ends when they do backend changes.
>
> I don't believe that, they would just say, "oh, it is broken" or "oh,
> it is not a primary language" or whatever excuse.
You probably don't follow GCC developmen
20 matches
Mail list logo
