Mark Mitchell <[EMAIL PROTECTED]> writes:
| Gabriel Dos Reis wrote:
|
| > The resason here is that, after we complained that A is incomplete
| > (therefore cannot be used as return type in the function definition),
| > cp/decl.c:check_function_type() changes the return type to void, thus
| > giv
I just tried to check in a change on the 4.1 branch. I get this
nice little message :
svn: Commit failed (details follow):
svn: Authorization failed
svn: Your commit message was left in a temporary file:
svn:'/fuel98/export/svn/gcc-4_1-branch/svn-commit.2.tmp'
Suggestions?
jeff
On Tue, Nov 29, 2005 at 10:01:25PM +, Joern RENNECKE wrote:
> >If we use MIN (tree_low_cst (TYPE_SIZE (type), 0), BIGGEST_ALIGNMENT)
> >here, I'm afraid that would be much bigger ABI incompatibility.
> >Currently, say
> >typedef char __attribute__((vector_size (64))) v64qi;
> >is 64 bytes align
Jeffrey A Law wrote:
I just tried to check in a change on the 4.1 branch. I get this
nice little message :
svn: Commit failed (details follow):
svn: Authorization failed
svn: Your commit message was left in a temporary file:
svn:'/fuel98/export/svn/gcc-4_1-branch/svn-commit.2.tmp'
You pro
Jakub Jelinek wrote:
On Tue, Nov 29, 2005 at 10:01:25PM +, Joern RENNECKE wrote:
If we use MIN (tree_low_cst (TYPE_SIZE (type), 0), BIGGEST_ALIGNMENT)
here, I'm afraid that would be much bigger ABI incompatibility.
Currently, say
typedef char __attribute__((vector_size (64))) v64qi;
is 6
GCC 4.0.x on s390{,x} aligned vector_size 1/2/4/8/64/128/... types
to their size, just vector_size 16 and 32 has been 8 bytes aligned
(BIGGEST_ALIGNMENT).
It is just a side-effect of the 3.4/4.0 code - if there was a supported
integer mode on the target for the requested size, then alignment of
On Wed, 2005-11-30 at 02:01 -0700, Jeffrey A Law wrote:
> I just tried to check in a change on the 4.1 branch. I get this
> nice little message :
>
> svn: Commit failed (details follow):
> svn: Authorization failed
> svn: Your commit message was left in a temporary file:
> svn:'/fuel98/export
Hello!
This PR is about missing USER_LABEL_PREFIX for static variables. The issue
was fixed for 4.0, but for 3.4 there won't be a fix as stated in the audit
trail by Mark Mitchell in comment #15. He probably based his decision on
comment #14, where Geoff Keating states that this bug does only affe
Hello!
Maybe you got this type of mails, but maybe not. So i send it. :)
Could you put an option into the compiler, to produce other error / warning
outputs?
The "file.c:line: error message" format is ok, but the stupid visual studio
(which i use (good editor)) knows only the "file.c(line): err
YaniMan wrote:
Hello!
Maybe you got this type of mails, but maybe not. So i send it. :)
Could you put an option into the compiler, to produce other error /
warning outputs?
The "file.c:line: error message" format is ok, but the stupid visual
studio (which i use (good editor)) knows only the "f
"YaniMan" <[EMAIL PROTECTED]> wrote:
> Or these messages should going (by an option) to the stdout rather than
> stderr, so i can write a parser (gcc a.c | myparser) to convert the
> messages.
gcc a.c 2>&1 | myparser >&2
paul
On Wed, Nov 23, 2005 at 03:32:57PM +0100, Jakub Jelinek wrote:
> While doing svn diff, I've noticed
> gcc/config/i386/xm-dgux.h
> gcc/config/i386/xm-sysv3.h
> gcc/config/i386/xm-sun.h
> gcc/config/i386/scodbx.h
> files popped out of nowhere on the trunk (and through 4.1 branching
> also on gcc-4_1-
On Wed, 2005-11-30 at 16:49 +0100, Gunther Nikl wrote:
> On Wed, Nov 23, 2005 at 03:32:57PM +0100, Jakub Jelinek wrote:
> > While doing svn diff, I've noticed
> > gcc/config/i386/xm-dgux.h
> > gcc/config/i386/xm-sysv3.h
> > gcc/config/i386/xm-sun.h
> > gcc/config/i386/scodbx.h
> > files popped out
On Wed, Nov 30, 2005 at 10:57:42AM -0500, Daniel Berlin wrote:
> On Wed, 2005-11-30 at 16:49 +0100, Gunther Nikl wrote:
> > I retrieved gcc-2_95-branch from the svn repository and diffed it with
> > my CVS checkout. The diff contained lots of differences.
> > Many files had different CVS $Id string
[EMAIL PROTECTED] said:
> Or these messages should going (by an option) to the stdout rather than
> stderr, so i can write a parser (gcc a.c | myparser) to convert the
> messages.
Ah, but that option does exist already:
gcc a.c 2>&1 | myparser
:-)
Christi
YaniMan wrote:
> Hello!
>
> Maybe you got this type of mails, but maybe not. So i send it. :)
Hey! Maybe you got this type of replies, but maybe not. So I send it too!
:)
> Could you put an option into the compiler, to produce other error /
> warning outputs?
> The "file.c:line: error messag
On Wed, 2005-11-30 at 13:44 +0100, Paolo Bonzini wrote:
> You probably are on a svn:// tree. Try something along the lines of
Ahhh.
> svn switch --relocate {svn://,svn+ssh://[EMAIL PROTECTED]/svn/gcc
Thanks. I doubt I would have come up with that one on my own! :-)
jeff
Gunther Nikl <[EMAIL PROTECTED]> writes:
> This PR is about missing USER_LABEL_PREFIX for static variables. The issue
> was fixed for 4.0, but for 3.4 there won't be a fix as stated in the audit
> trail by Mark Mitchell in comment #15. He probably based his decision on
> comment #14, where Geoff K
Gabriel Dos Reis wrote:
Would prefer to have
build_function_type() also modified to be nice to error_mark_node?
Yes, I see no reason for it not to.
Jason
On Tue, Nov 29, 2005 at 10:58:32PM +, Joseph S. Myers wrote:
> (Incidentally, why does libgcc-std.ver not include __unordxf2 and
> __unordtf2 although it has __unordsf2 and __unorddf2?)
I'm sure it wasn't intentional.
r~
Hi,
What is the prefered way to add a new target OS for GCC?
I've added the support to an older version of GCC (2.95)
but don't want to redo the work as GCC evolves.
Regards,
Leif Ekblad
www.rdos.net/rdos
Gunther Nikl wrote:
> Hello!
>
> This PR is about missing USER_LABEL_PREFIX for static variables. The issue
> was fixed for 4.0, but for 3.4 there won't be a fix as stated in the audit
> trail by Mark Mitchell in comment #15. He probably based his decision on
> comment #14, where Geoff Keating sta
> What is the prefered way to add a new target OS for GCC? I've added
> the support to an older version of GCC (2.95) but don't want to redo
> the work as GCC evolves.
The best thing to do is to get the port up to scratch relative to the
current mainline version and then contribute it to the GCC
Mark Mitchell <[EMAIL PROTECTED]> writes:
| Gunther Nikl wrote:
| > Hello!
| >
| > This PR is about missing USER_LABEL_PREFIX for static variables. The issue
| > was fixed for 4.0, but for 3.4 there won't be a fix as stated in the audit
| > trail by Mark Mitchell in comment #15. He probably based
In cp/parser.c:cp_parser_declaration(), we have the following code
/* Try to figure out what kind of declaration is present. */
token1 = *cp_lexer_peek_token (parser->lexer);
if (token1.type != CPP_EOF)
token2 = *cp_lexer_peek_nth_token (parser->lexer, 2);
else
token2.type = tok
Hi ,
I am new to gcc and shell commands. I am trying to compile my code using gcc
3.3.2 provided with AMD Au1550 development CD. When I compile my code, I get an
error message with undefined references to printf and other file i/o functions.
I saw a couple of emails in the forum with the same
On Nov 30, 2005, at 7:49 AM, Gunther Nikl wrote:
There seem to be more conversion glichtes. I retrieved gcc-2_95-branch
from the svn repository and diffed it with my CVS checkout. The diff
contained lots of differences.
Many files had different CVS $Id strings.
I was told that this is harmless
On Wed, 2005-11-30 at 14:53 -0800, Mike Stump wrote:
> On Nov 30, 2005, at 7:49 AM, Gunther Nikl wrote:
> > There seem to be more conversion glichtes. I retrieved gcc-2_95-branch
> > from the svn repository and diffed it with my CVS checkout. The diff
> > contained lots of differences.
> > Many fil
On Nov 30, 2005, at 2:40 PM, pati (sent by Nabble.com) wrote:
I am trying to compile my code using gcc 3.3.2 provided with AMD
Au1550 development CD.
Wrong forum for this question.
$(LD) -$(ENDIAN) -T test.ld -G 0 $(OBJS) -o $(NAME).elf
Don't use ld to link, use gcc to link.
For the last few months, gcc 4.1 has had problems compling
the following code in posRMSDPot.cc in xplor-nih...
IStringStream iNoComments( stripped );
// read NOEPot table
CDSStringStreamBuf dum;
while ( !iNoComments.eof() && !iNoComments.fail() ) {
String word; iNoComments >> word;
Hi all
I am porting GCC compiler to new 16 bit target. I am using GCC-4.0.x
For one of the target specific options, I am using PSI mode for
representing pointers.
If I compile the following test code with this target specific option
along with any of the optimization options I am getting an ICE.
> I have also provided RTL's for "extendpsisi" and "truncsipsi" (for
> converting between PSI and SI modes).
You need extendpsisi2, truncsipsi2, and zero_extendpsisi2. The m32c
port uses PSI for pointers also; you can use it as an example.
32 matches
Mail list logo