--- Comment #21 from paolo at gcc dot gnu dot org 2005-11-24 01:29 ---
Subject: Bug 24975
Author: paolo
Date: Thu Nov 24 01:29:51 2005
New Revision: 107447
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107447
Log:
2005-11-23 Paolo Carlini <[EMAIL PROTECTED]>
PR libst
Today's CVS (pardon, SVN):
gmake[3]: Entering directory `/usr/home/mckelvey/software/gcc-obj/gcc'
gmake[3]: Nothing to be done for `all'.
gmake[3]: Leaving directory `/usr/home/mckelvey/software/gcc-obj/gcc'
if [ xinfo = xinfo ]; then \
makeinfo --split-size=500 --no-split -I . -I ../.
--- Comment #3 from gdr at gcc dot gnu dot org 2005-11-24 02:02 ---
Subject: Bug 21667
Author: gdr
Date: Thu Nov 24 02:02:26 2005
New Revision: 107448
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=107448
Log:
2005-11-23 Gabriel Dos Reis <[EMAIL PROTECTED]>
PR c++/216
--- Comment #4 from gdr at gcc dot gnu dot org 2005-11-24 02:10 ---
Fixed on mainline.
--
gdr at gcc dot gnu dot org changed:
What|Removed |Added
Status|NEW
--- Comment #4 from gdr at gcc dot gnu dot org 2005-11-24 02:23 ---
Agreed with the reporter's analysis
--
gdr at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #3 from gdr at gcc dot gnu dot org 2005-11-24 02:25 ---
(In reply to comment #2)
> This is how C++ is done, maybe a warning can be emitted but it seems like it
> will emitt too much for
> valid C++ code.
>
I don't know; the code shown is very contrived to my taste.
--
--- Comment #12 from gdr at gcc dot gnu dot org 2005-11-24 02:35 ---
Mainline already has Richard's suggestion.
Closing.
--
gdr at gcc dot gnu dot org changed:
What|Removed |Added
This bug looks much like 24093 except that it fails on 4.1/4.2
Originally reported by Alexey Maximov <[EMAIL PROTECTED]>
#pragma interface
struct T
{
T *p;
void baz ()
{
p->baz ();
}
};
void foo (T *p)
{
p->baz ();
}
--
Summary: [4.1/4.2 regression] Segmentation faul
--- Comment #1 from belyshev at depni dot sinp dot msu dot ru 2005-11-24
02:42 ---
(In reply to comment #0)
> This bug looks much like 24093 except that it fails on 4.1/4.2
s/24093/bug 24248/
--
belyshev at depni dot sinp dot msu dot ru changed:
What|Removed
--- Comment #3 from gdr at gcc dot gnu dot org 2005-11-24 02:42 ---
(In reply to comment #2)
> IMO, saying "`bar()::X' uses local type `bar()::X'" makes no sense.
Agreed. Working a patch.
--
gdr at gcc dot gnu dot org changed:
What|Removed |Adde
--- Comment #1 from pinskia at gcc dot gnu dot org 2005-11-24 03:31 ---
Confirmed via Ben E. on IRC and there is a mailing to the GCC list about it
too.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from pinskia at gcc dot gnu dot org 2005-11-24 03:34 ---
Actually this is invalid, you need to build with a clean object directory.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #2 from pinskia at gcc dot gnu dot org 2005-11-24 03:35 ---
Confirmed.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
CC|
--- Comment #3 from gdr at integrable-solutions dot net 2005-11-24 03:38
---
Subject: Re: Bootstrap: Failure to build doc/gcc.info
"pinskia at gcc dot gnu dot org" <[EMAIL PROTECTED]> writes:
| Actually this is invalid, you need to build with a clean object directory.
That is bullsh
--- Comment #4 from gdr at gcc dot gnu dot org 2005-11-24 03:39 ---
Fixed on mainline
--
gdr at gcc dot gnu dot org changed:
What|Removed |Added
Status|ASSIGN
--- Comment #4 from gdr at gcc dot gnu dot org 2005-11-24 03:40 ---
still does not work with bubblestrap and friends
--
gdr at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #4 from dje at gcc dot gnu dot org 2005-11-24 03:56 ---
Many people are reporting that they cannot bootstrap GCC with IBM's VisualAge
compiler. This appears to be a problem with VAC/XLC, not with GCC. This bug
should be reported to IBM as a XLC bug. In the meantime, you ne
% make
gcc -E -g -DFRMWRK_POSIX -c -I . ./POSIX/FMutex.cpp
gcc: Internal error: Segmentation fault (program cc1plus)
Please submit a full bug report.
See http://gcc.gnu.org/bugs.html> for instructions.
*** Error code 1
Stop.
% gcc -v
Reading specs from /opt/gcc.3.3/lib/gcc-lib/i586-pc-interix3/3.3
--- Comment #5 from pinskia at gcc dot gnu dot org 2005-11-24 04:04 ---
(In reply to comment #4)
> still does not work with bubblestrap and friends
After a clean build?
See http://gcc.gnu.org/ml/gcc/2005-11/msg01173.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25009
--- Comment #6 from pinskia at gcc dot gnu dot org 2005-11-24 04:07 ---
(In reply to comment #3)
> Subject: Re: Bootstrap: Failure to build doc/gcc.info
> "pinskia at gcc dot gnu dot org" <[EMAIL PROTECTED]> writes:
> | Actually this is invalid, you need to build with a clean object dir
--- Comment #1 from pinskia at gcc dot gnu dot org 2005-11-24 04:27 ---
Can you read http://gcc.gnu.org/bugs.html, and attach the preprocessed source?
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #2 from viorel dot stolea at gmail dot com 2005-11-24 04:35
---
Subject: Re: gcc exits with core
pinskia at gcc dot gnu dot org wrote:
>--- Comment #1 from pinskia at gcc dot gnu dot org 2005-11-24 04:27
>---
>Can you read http://gcc.gnu.org/bugs.html, and attac
--- Comment #7 from pinskia at gcc dot gnu dot org 2005-11-24 04:50 ---
GNU make is changing so there is no reason for this bug to be opened any more.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #3 from viorel dot stolea at gmail dot com 2005-11-24 05:01
---
Subject: Re: gcc exits with core
pinskia at gcc dot gnu dot org wrote:
>--- Comment #1 from pinskia at gcc dot gnu dot org 2005-11-24 04:27
>---
>Can you read http://gcc.gnu.org/bugs.html, and attac
--- Comment #4 from pinskia at gcc dot gnu dot org 2005-11-24 05:07 ---
((In reply to comment #2)
> No (|*.i*|) file generated. (I've added |-save-temps but no luck|) sorry.
Hmm: gcc -E -g -DFRMWRK_POSIX -c -I . ./POSIX/FMutex.cpp
That means it is dieing while preprocessing.
Two things,
When I compiled the following program with gfortran, internal compiler
error occured.
I think the right behavior is that compilation is completed, and
printed "what is happen?" to standard output in execution.
module ucharfunc
contains
function foo(a) result(oresult)
character(len=*) :: a
When I compiled the following program with gfortran, internal compiler
error occured.
I think the right behavior is that compilation is completed, and
printed "what is happen?" to standard output in execution.
module ucharfunc
contains
function foo(a) result(oresult)
character(len=*) :: a
--- Comment #1 from pinskia at gcc dot gnu dot org 2005-11-24 06:04 ---
*** This bug has been marked as a duplicate of 25012 ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #1 from pinskia at gcc dot gnu dot org 2005-11-24 06:04 ---
*** Bug 25013 has been marked as a duplicate of this bug. ***
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25012
--- Comment #2 from pinskia at gcc dot gnu dot org 2005-11-24 06:06 ---
This is an exact dup of PR 15326 which has been fixed for 4.1.0 and above.
*** This bug has been marked as a duplicate of 15326 ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed
--- Comment #16 from pinskia at gcc dot gnu dot org 2005-11-24 06:06
---
*** Bug 25012 has been marked as a duplicate of this bug. ***
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #3 from pinskia at gcc dot gnu dot org 2005-11-24 06:14 ---
XPASS: gcc.dg/tree-ssa/bool-7.c scan-tree-dump-times != 1 0
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24989
--- Comment #7 from amodra at bigpond dot net dot au 2005-11-24 06:51
---
I'm not surprised that reducing this testcase isn't easy. Register pressure is
needed to trigger the bug. The problem is that in
(insn:HI 2761 3601 2769 279 wmadec.c:1117 (set (reg:V4SF 280 [ vect_var_.655 ])
--- Comment #8 from amodra at bigpond dot net dot au 2005-11-24 07:04
---
Oops, no, that's not a stack slot. That's a stack slot gone wrong. Where's
the MEM for the slot?
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24997
--- Comment #7 from jvdelisle at gcc dot gnu dot org 2005-11-24 07:21
---
This is not a bug. Gfortran is complying with F95 namelist read requirements.
This would be an enhancement or extension. The work around is to use correct
array triplets in the array qualifiers for namelist read
101 - 135 of 135 matches
Mail list logo
