--- Additional Comments From ramana dot radhakrishnan at codito dot com
2005-04-22 07:43 ---
If the above patch set is applied for 3.3.6, please also apply this patch so
that the build does not break.
--- Additional Comments From b dot gunreben at web dot de 2005-04-22 08:01
---
I just tested on a compiler without additional patches at all. The version is
g++ (GCC) 4.0.0 20050415, means CVS from april 15th. I still get the same bug.
--
I try to compile gcc 4.0.0 but make fails.
Configured with ./configure --prefix=/usr --enable-shared
After make I got ...
configure: creating ./config.status
config.status: creating Makefile
config.status: executing default-1 commands
./config.status: line 910:
--
What|Removed |Added
Summary|cannot compile gcc and zlib-|cannot compile gcc with
|1.2.2 |zlib-1.2.2
Hi everybody,
I have a product. It has been written using C++.
I have the need to compile it, on Aix 5.1 with g++ 3.4.3.
GCC as well as G++ source codes have been downloaded as from the gnu ftp
site.
After configuration, I launch the make, but I have this problem:
/tmp//ccWSbEX3.s:
The gcc-4.0 manual says
* An expression-statement or the left-hand side of a comma
expression contains no side effects. To suppress the
warning, cast the unused expression to void. For example, an
expression such as `x[i,j]' will cause a warning, but
--- Additional Comments From bruno at clisp dot org 2005-04-22 11:01
---
Created an attachment (id=8706)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8706action=view)
source file foo.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21159
--- Additional Comments From bruno at clisp dot org 2005-04-22 11:01
---
Created an attachment (id=8707)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8707action=view)
source file bug.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21159
When a function contains a call to longjmp(), some variables give the
warning
variable 'ptr' might be clobbered by 'longjmp' or 'vfork'
How to avoid this warning? In earlier versions of gcc, it was possible to
write
(void)ptr;
in order to force ptr on the stack, where it would be
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-22
11:04 ---
*** This bug has been marked as a duplicate of 17383 ***
--
What|Removed |Added
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-22
11:04 ---
*** Bug 21158 has been marked as a duplicate of this bug. ***
--
What|Removed |Added
--- Additional Comments From bruno at clisp dot org 2005-04-22 11:04
---
Created an attachment (id=8708)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8708action=view)
source file bug.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21160
The warning
argument 'obj' might be clobbered by 'longjmp' or 'vfork'
does not take into account the facts that
1) When longjmp() is called, setjmp() returns a non-null value,
2) In this case, when setjmp() returns a non-null value, 'obj' is
reset before being used.
--- Additional Comments From bruno at clisp dot org 2005-04-22 11:08
---
Created an attachment (id=8709)
-- (http://gcc.gnu.org/bugzilla/attachment.cgi?id=8709action=view)
source file bug.c
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21161
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-22
11:18 ---
Use volatile qualifier.
The reason why (void)a; worked before well we are not optimizating as much as
before.
--
What|Removed |Added
--
What|Removed |Added
Severity|normal |minor
Keywords||diagnostic
Summary|no effect warning despite
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-22
11:23 ---
Confirmed.
--
What|Removed |Added
Status|UNCONFIRMED |NEW
--- Additional Comments From keller at fs-net dot de 2005-04-22 12:16
---
Sorry, I made a mistake. I misinterpreted how the 68000 assembler instruction
UNLK works. The stack correction is in fact not required, so the generated code
can be considered correct.
I had an error in my code
Hi I cannot build gcc-4.0.0 on ia64 linux:
/bin/sh ./libtool --mode=compile
/scratch/q127038/gcc-objects-IA64LX/gcc/xgcc
-B/scratch/q127038/gcc-objects-IA64LX/gcc/
-B/share/sdmfs1/GNU/MSC-2002IA.March/usr/local//ia64-unknown-linux-gnu/bin/
--- Additional Comments From fxcoudert at gcc dot gnu dot org 2005-04-22
12:42 ---
This prevents compiling the common iso_varying_string module by Rich Townsend.
--
What|Removed |Added
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-04-22
12:59 ---
Subject: Bug 12913
CVSROOT:/cvs/gcc
Module name:gcc
Branch: gcc-4_0-branch
Changes by: [EMAIL PROTECTED] 2005-04-22 12:58:43
Modified files:
gcc:
--- Additional Comments From tobi at gcc dot gnu dot org 2005-04-22 13:09
---
Or, alternatively, we could call reshape_generic. Which of course would be evil
from a performance standpoitn :-)
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21127
--- Additional Comments From tobi at gcc dot gnu dot org 2005-04-22 13:17
---
It's only implicit in your bug report so I'll ask: are you saying that your
module's file name contains a capital letter? I highly doubt that this is
possible.
Or, can you please provide more detail if the
--- Additional Comments From tobi at gcc dot gnu dot org 2005-04-22 13:21
---
I think you copy/pasted the wrong working testcase.
--
What|Removed |Added
CC|
--- Additional Comments From tobi at gcc dot gnu dot org 2005-04-22 13:33
---
It should be easy enough to detect at compile-time. I haven't yet looked up
which part of the standard renders this invalid.
BTW thanks Joost!
--
What|Removed |Added
--- Additional Comments From rakdver at gcc dot gnu dot org 2005-04-22
13:56 ---
As far as I can tell, the code at .final_cleanup dump is correct,
so the patch most likely reveals some latent bug in sms or one of
the later passes.
--
What|Removed
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-22
14:07 ---
Fixed.
--
What|Removed |Added
Status|ASSIGNED|RESOLVED
--
Bug 16989 depends on bug 12913, which changed state.
Bug 12913 Summary: [4.0 Regression] Jumps into variable length array scope not
rejected
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=12913
What|Old Value |New Value
--- Additional Comments From bruno at clisp dot org 2005-04-22 14:14
---
I don't understand your resolution.
How can I guarantee that gcc will not put 'ptr' and 'array' into registers
where, on SPARC,
longjmp() will clobber them?
The semantics of 'volatile' are quite different
--- Additional Comments From tobi at gcc dot gnu dot org 2005-04-22 14:17
---
I didn't find anything requiring this in the standard, and it would seem weird,
given that SAVE is implicit in several cases. See also note 4.27.
--
What|Removed |Added
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-22
14:24 ---
(In reply to comment #3)
I have taken the address of 'ptr' and despite that, it was not excluded from
the candidates
for register allocation - or the warning occurred despite of the variable
being
--- Additional Comments From tobi at gcc dot gnu dot org 2005-04-22 14:30
---
That's the problem. I'm fairly sure Joost knows the problems for all these
bugs ...
--
What|Removed |Added
--- Additional Comments From pinskia at gcc dot gnu dot org 2005-04-22
14:31 ---
See http://gcc.gnu.org/ml/gcc/2004-06/msg01035.html also.
Also the following will work:
asm volatile ( : : p (a));
instead of
(void)a;
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=21160
--- Additional Comments From tobi at gcc dot gnu dot org 2005-04-22 14:33
---
Are there any circumstances where the argument to NULL has any meaning, besides
making a program invalid?
--
What|Removed |Added
--- Additional Comments From tobi at gcc dot gnu dot org 2005-04-22 14:36
---
Any pointers as to why this is invalid?
--
What|Removed |Added
CC|
--- Additional Comments From cvs-commit at gcc dot gnu dot org 2005-04-22
14:36 ---
Subject: Bug 20813
CVSROOT:/cvs/gcc
Module name:gcc
Changes by: [EMAIL PROTECTED] 2005-04-22 14:36:37
Modified files:
gcc: ChangeLog
--
What|Removed |Added
Status|UNCONFIRMED |NEW
Ever Confirmed||1
Keywords|
37 matches
Mail list logo
