--- Comment #14 from fxcoudert at gcc dot gnu dot org 2007-01-10 08:11
---
In emit_move_insn, the failing assert is:
(gdb) l 3275
3270{
3271 enum machine_mode mode = GET_MODE (x);
3272 rtx y_cst = NULL_RTX;
3273 rtx last_insn, set;
3274
3275 gcc_assert (mode !=
--- Comment #15 from pinskia at gcc dot gnu dot org 2007-01-10 09:07
---
The result decl should have a RTL of a DI mode:
unsigned ignored regdecl DI file a.f90 line 1 size unit size
align 64 context
(reg:SI 122 [ ])>
The mode of the decl is correct but the
--- Comment #3 from rguenth at gcc dot gnu dot org 2007-01-10 09:22 ---
Hmmhm, this is probably invalid. :/
--
rguenth at gcc dot gnu dot org changed:
What|Removed |Added
../../../libjava/sun/misc/natUnsafe.cc: In member function 'virtual void
sun::misc::Unsafe::putIntVolatile(java::lang::Object*, jlong, jint)':
../../../libjava/sun/misc/natUnsafe.cc:159: error: 'write_barrier' was not
declared in this scope
../../../libjava/sun/misc/natUnsafe.cc: In member function
g++42 -v
Using built-in specs.
Target: x86_64-portbld-freebsd6.2
Configured with: ./..//gcc-4.2-20070102/configure --disable-nls
--with-system-zlib --with-libiconv-prefix=/usr/local --with-gmp=/usr/local
--program-suffix=42 --libdir=/usr/local/lib/gcc-4.2.0
--with-gxx-include-dir=/usr/local/lib/gcc
--- Comment #1 from chat95 at mac dot com 2007-01-10 10:48 ---
Created an attachment (id=12878)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12878&action=view)
a testcase actually used file. from octave-2.9.9
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30423
--- Comment #55 from mkuvyrkov at gcc dot gnu dot org 2007-01-10 11:42
---
Created an attachment (id=12879)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12879&action=view)
Patch for scheduler dependency lists.
Hi,
This patch introduces new dependency lists to scheduler thus mak
I got
/net/gnu-13/export/gnu/src/gcc/gcc/libjava/sun/misc/natUnsafe.cc: In member
function 'virtual void sun::misc::Unsafe::putIntVolatile(java::lang::Object*,
jlong, jint)':
/net/gnu-13/export/gnu/src/gcc/gcc/libjava/sun/misc/natUnsafe.cc:159: error:
'write_barrier' was not declared in this scope
--- Comment #4 from hjl at lucon dot org 2007-01-10 13:31 ---
Created an attachment (id=12880)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12880&action=view)
A patch
This is a patch I am using. My gcc checkout tree is readonly. I use symlink to
create a writable tree. "cp -pR" d
--- Comment #4 from lucier at math dot purdue dot edu 2007-01-10 14:50
---
This problem no longer occurs.
--
lucier at math dot purdue dot edu changed:
What|Removed |Added
---
--- Comment #1 from hjl at lucon dot org 2007-01-10 14:55 ---
Created an attachment (id=12881)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12881&action=view)
A patch
I am testing this patch.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30424
[ Forwarded from http://bugs.debian.org/406324 ]
Alexei Sheplyakov reports that gcc 3.4, 4.0 and 4.1 produces an ICE on the
following invalid code:
namespace A {
class ex;
struct f { f(const ex& x); };
}
namespace B {
template inline A::f g(const T& p) {
r
--- Comment #1 from tromey at gcc dot gnu dot org 2007-01-10 15:37 ---
The other bug has a proposed patch.
*** This bug has been marked as a duplicate of 30424 ***
--
tromey at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #2 from tromey at gcc dot gnu dot org 2007-01-10 15:37 ---
*** Bug 30422 has been marked as a duplicate of this bug. ***
--
tromey at gcc dot gnu dot org changed:
What|Removed |Added
-
--- Comment #3 from hjl at lucon dot org 2007-01-10 15:48 ---
(In reply to comment #1)
> Created an attachment (id=12881)
--> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12881&action=view) [edit]
> A patch
>
> I am testing this patch.
>
It fixes the issue:
http://gcc.gnu.org/ml/g
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-01-10 16:34 ---
% ./gendoc
/libexec/ld-elf.so.1: ./gendoc: Undefined symbol "_ZNSo9_M_insertEPKcl"
This makes it sound like libstdc++'s ABI has changed slightly but just in a
forwards compatiable way.
Can you try to force using
--- Comment #4 from aph at gcc dot gnu dot org 2007-01-10 16:51 ---
That patch is fine.
--
aph at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCO
--- Comment #5 from hjl at gcc dot gnu dot org 2007-01-10 17:51 ---
Subject: Bug 30424
Author: hjl
Date: Wed Jan 10 17:50:40 2007
New Revision: 120645
URL: http://gcc.gnu.org/viewcvs?root=gcc&view=rev&rev=120645
Log:
2007-01-10 H.J. Lu <[EMAIL PROTECTED]>
PR libgcj/30424
--- Comment #6 from hjl at lucon dot org 2007-01-10 17:51 ---
Fixed.
--
hjl at lucon dot org changed:
What|Removed |Added
Status|NEW |
--- Comment #5 from tromey at gcc dot gnu dot org 2007-01-10 18:06 ---
I have a patch to update the docs.
--
tromey at gcc dot gnu dot org changed:
What|Removed |Added
--- Comment #19 from rguenth at gcc dot gnu dot org 2007-01-10 18:39
---
We'll see with tonights run of the tester. Thanks.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30089
/pkgs/gmp-4.2.1 --with-mpfr=/pkgs/gmp-4.2.1
Thread model: posix
gcc version 4.2.0 20070110 (prerelease)
The two hot spots were
tree SSA to normal: 52.63 (16%) usr 0.04 ( 0%) sys 52.69 (15%) wall
55617 kB ( 8%) ggc
tree FRE : 150.81 (46%) usr 0.20 ( 2%) sys 154.00 (45%)
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||ice-on-valid-code
Known to work||4.2
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||build
Known to work||4.2.0
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28986
--- Comment #10 from pcarlini at suse dot de 2007-01-10 18:56 ---
(In reply to comment #8)
> Paolo -- there is what the standard says, and what we can or should implement.
> I believe there is a genuine bug in the standard here, no matter how
> easy it is to avoid the segmentation fault.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27845
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Known to work||4.2.0
Target Milestone|--- |4.3.0
http://
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29992
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30081
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30190
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-01-10 18:59 ---
Reopening to ...
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-01-10 18:59 ---
Mark as invalid.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30202
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30236
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Known to fail||4.0.4 3.4.0 3.3.3 3.2 4.1.1
Known to work|
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.1.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24459
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30238
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30237
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||build, ice-on-valid-code
Known to work|
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25818
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30084
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30371
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29624
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||wrong-code
Known to fail||4.1.1 4.0.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30034
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||EH, wrong-code
Known to work||4.2.0
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||EH, wrong-code
Known to work||4.2.0
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||EH, wrong-code
Known to work||4.2.0
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||EH, wrong-code
Known to work||4.2.0
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||EH, wrong-code
Summary|FAIL: g++.old- |[4.3 R
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||EH, wrong-code
Known to work||4.2.0
--- Comment #4 from dave at hiauly1 dot hia dot nrc dot ca 2007-01-10
19:11 ---
Subject: Re: [4.3 Regression] gcc/libssp/ssp.c:177: ICE: in
cgraph_expand_all_functions, at cgraphunit.c:1220
This is now fixed. Not sure which patch.
Dave
--
http://gcc.gnu.org/bugzilla/show_bug.cg
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Keywords||EH, wrong-code
Known to work||4.2.0
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25135
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23060
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27900
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24325
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Known to fail||3.3.3 3.4.0 4.0.0 4.1.0
|
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30263
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Summary|compiling linux kernels |[4.2/4.3 Regression]
|2.6.16.14/15 2.6.17-rc3 on |
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.1.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29581
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29802
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29965
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29947
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30172
--- Comment #11 from pcarlini at suse dot de 2007-01-10 19:18 ---
Forgot: assuming we imagine the standard clarified per your proposal on LWG (or
read as such for all practical matters), I understand that not segfaulting when
size == 0 would be a conforming behavior. Then, in v3, we coul
--- Comment #5 from pinskia at gcc dot gnu dot org 2007-01-10 19:19 ---
I am very sure it was:
http://gcc.gnu.org/ml/gcc-patches/2007-01/msg00565.html
And/or the one I indenfy before.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30349
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30179
--- Comment #6 from pinskia at gcc dot gnu dot org 2007-01-10 19:20 ---
Fixed.
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Status|NEW
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28790
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25261
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29341
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26899
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=29629
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30197
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.3.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30180
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Known to work||4.1.2
Target Milestone|--- |4.2.0
http://
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=24959
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23745
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.1.2
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=27959
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28427
--
pinskia at gcc dot gnu dot org changed:
What|Removed |Added
Target Milestone|--- |4.2.0
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=28797
--- Comment #25 from amacleod at redhat dot com 2007-01-10 19:47 ---
There were numerous factors in the mainline speedup of SSA->normal, including a
massive rewrite, but there are a couple of big wins that are backportable, and
were in fact considered. It was just that they were too late
--- Comment #4 from pluto at agmk dot net 2007-01-10 19:58 ---
hmm, if i remove this huge amount of pci*info* data structures
hog doesn't present.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30052
The tiny test program below produces a warning (specifics commented in code
below). From my understanding, no warning should appear on compilation.
Current workaround: Warning disappears once line 2 (right after #include) is
uncommented.
Code:
--
--- Comment #1 from schwab at suse dot de 2007-01-10 20:37 ---
strndup is a GNU extension and is only declared in when _GNU_SOURCE
is defined.
--
schwab at suse dot de changed:
What|Removed |Added
--
--- Comment #2 from pinskia at gcc dot gnu dot org 2007-01-10 20:38 ---
Not a bug, strndup is a GNU (glibc) extension. You have to use -D_GNU_SOURCE
when compiling.
The warning messages are correct as there is no prototype for strndup.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id
Testcase:
#define vector __attribute__((vector_size(16) ))
vector float a;
int f(void)
{
a = ~a;
}
---
This is rejected with the C++ front-end:
t.c: In function 'int f()':
t.c:7: error: wrong type argument to bit-complement
--
Summary: ~ vector float is accepted
Both the C and C++ front-end accept this:
#define vector __attribute__((vector_size(16) ))
vector float a;
vector float b;
int f(void)
{
a = a | b;
}
---
xor and bitwise and is effected too.
--
Summary: vector float | vector float is accepted
Product: g
--- Comment #11 from pault at gcc dot gnu dot org 2007-01-10 20:57 ---
Kaveh and David,
>
> Well, you need to be using the 4.0 branch, not 4.1. I see that an IA64 report
> occurs here with the current 4.0.4 prerelease:
If you look at the Bugzilla entries for the two PRs, they were onl
--- Comment #12 from pault at gcc dot gnu dot org 2007-01-10 21:00 ---
In fact, I will clear it myself, since I am sure that you will do the deleting!
Paul
--
pault at gcc dot gnu dot org changed:
What|Removed |Added
--
--- Comment #3 from pinskia at gcc dot gnu dot org 2007-01-10 21:28 ---
Testing a better patch.
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30297
--- Comment #13 from ghazi at gcc dot gnu dot org 2007-01-10 21:45 ---
Paul - The bug is not "FIXED" in 4.0, please don't mark it as such yet.
"WONTFIX" may be a more accurate description if that is the group decision.
You can remove yourself from the assigned field if you aren't able
--- Comment #14 from paulthomas2 at wanadoo dot fr 2007-01-10 22:09 ---
Subject: Re: testsuite failures in actual_array_constructor_2.f90
and actual_array_substr_2.f90
Kaveh
> --- Comment #13 from ghazi at gcc dot gnu dot org 2007-01-10 21:45
> ---
> Paul - The bug is not "
[EMAIL PROTECTED]> gcc -g -W -Wall xxq.c
xxq.c: In function `memcheck_posix_memalign':
xxq.c:23: internal compiler error: in emit_move_insn, at expr.c:2809
Please submit a full bug report,
with preprocessed source if appropriate.
See http://gcc.gnu.org/bugs.html> for instructions.
[EMAIL PROTECTED]
$ cat a.f90
module truc
end module truc
module bar
use truc
end module bar
use bar
end
$ gfortran a.f90
$ gfortran a.f90 -Jfoo
f951(1968) malloc: *** Deallocation of a pointer not malloced: 0x41304a90; This
could be a double free(), or free() called with the middle of an allocated
block; Try s
--
fxcoudert at gcc dot gnu dot org changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Ever Confirmed|0 |1
Last
--- Comment #16 from pinskia at gcc dot gnu dot org 2007-01-10 22:51
---
The type is correct when the decl is created:
Breakpoint 3, build_decl_stat (code=RESULT_DECL, name=0x0, type=0xb7c55384) at
../../gcc/tree.c:3250
3250 t = make_node_stat (code PASS_MEM_STAT);
(gdb) p debug_ge
--- Comment #17 from pinskia at gcc dot gnu dot org 2007-01-10 22:56
---
hard_function_value returns the wrong rtl ...
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=30406
1 - 100 of 129 matches
Mail list logo