Joseph S. Myers wrote:-
> for that case. To quote my message:
>
> Consider the code
>
> int a, b, c, d, e, f;
> void *p1(void), *p2(void), *p3(void);
> int c1(void), c2(void);
> int d1(void), d2(void), d3(void);
> int z1(void), z2(void), z3(void);
>
> int
>
Ginil wrote:
code that compiled easily with gcc-3.2.1 would not compile with gcc-4.0.1.
... The major errors are with
template, name lookup but there are also certain errors with finding
definitions from header files which are included and are in include path.
Your code is probably not C++ stan
On Sat, 6 May 2006, Mike Stump wrote:
> I'll entertain pointers to VLA/VM and [*] bugs for C, please send me pointers
> to reports in bugzilla.
>
> Thanks.
>
> I know about http://gcc.gnu.org/PR25802
Bugs 19771, 7948, 18740 (in general, look at the bugs on which bug 16989
depends). The questi
Martin Reinecke <[EMAIL PROTECTED]> writes:
> I'm trying to learn about GCC's support for vector arithmetic and found
> the section "Using vector instructions through built-in functions", which
> answers a lot of questions, but unfortunately does not address things
> like gathering scalar values i
I'll entertain pointers to VLA/VM and [*] bugs for C, please send me
pointers to reports in bugzilla.
Thanks.
I know about http://gcc.gnu.org/PR25802
I also would like to know what people think the standard (c99) says
about:
void foo4(int o[*][4]) { }
void foo5(int o[4][*]) { }
void foo6(
May 2006
This is the eleventh code drop of the GCC front-end for
the PL/I programming language.
PL/I for GCC is released under the terms of the
GNU Public License; version 2.
Version 0.0.11 includes a new infrastructure for the preprocessor.
It has been more than a year since the previous rel
On May 4, 2006, at 4:44 PM, [EMAIL PROTECTED] wrote:
struct C : A, B { /* ... */ };
I am sorry to say that I don't understand the definition of struct C.
C is derived from A and B. Only valid of course in C++.
I see lots of failures running the testsuite on x86-64 now:
one example:
FAIL: gcc.c-torture/compile/2120-2.c -O3 -fomit-frame-pointer (test for
excess error
s)
Excess errors:
/cvs/gcc-svn/trunk/gcc/testsuite/gcc.c-torture/compile/2120-2.c:11:
internal compiler
error: RTL check: expe
From: Andrew Pinski <[EMAIL PROTECTED]>
To: "sean yang" <[EMAIL PROTECTED]>
CC: gcc@gcc.gnu.org
Subject: Re: indirect call in RTL dump files
Date: Sat, 6 May 2006 10:10:16 -0700
On May 6, 2006, at 10:06 AM, sean yang wrote:
2) indirect call (explained in 3.1 in the above paper)
Can someone
Snapshot gcc-4.2-20060506 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/4.2-20060506/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 4.2 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/trunk
On May 6, 2006, at 10:06 AM, sean yang wrote:
2) indirect call (explained in 3.1 in the above paper)
Can someone help me explain this a bit? --what the corresponding
code is in C, and what causes it to happen? What does the RTL code
look like?
void f(void (*x)(void))
{
x();
}
-- Pins
http://gcc.fyxm.net/summit/2004/GCC%20Call%20Graph.pdf
For the RTL representation, there are two type of function call instructions
as I understand.
1) direct call---this type of calls are shown with something like
(call (mem:QI (symbol_ref:SI ("bar") [flags 0x3] bar>) [0 S1 A8])
And the corre
12 matches
Mail list logo