At Thu, 21 Jul 2005 13:11:05 +0900,
GOTO Masanori wrote:
> The current gcc-4.0 can't compile the experimental glibc 2.3.5-2 with
> unstable gcc-4.0 (4.0.1-2) on m68k, due to gcc-4.0's Internal Compiler
> Error. Note that this problem was not occured with gcc-3.4 (3.4.4-5)
> with -O1/-O2/-O3.
You
Package: gcc-4.0
Version: 4.0.1-2
Severity: important
The current gcc-4.0 can't compile the experimental glibc 2.3.5-2 with
unstable gcc-4.0 (4.0.1-2) on m68k, due to gcc-4.0's Internal Compiler
Error. Note that this problem was not occured with gcc-3.4 (3.4.4-5)
with -O1/-O2/-O3.
gcc-4.0 with -
Package: g++
Version: 4.0.0-2
Severity: normal
Hi, I've found a regression in g++-4.0 when optimization is turned on.
Compile the attached example source code with:
g++ -Wall -O3 -c bug.cc
g++ produces the warning:
bug.cc:9: warning: control may reach end of non-void function 'char* f(c
Package: gfortran
Version: 4.0.0-2
Hello
its my first time reporting a bug. I started trying
the new
gfortran-4.0
and it seems to have some problem when executing a
code with a "SPREAD" function:
*
[EMAIL PROTECTED]:~/entanglement$ cat p.f90
program hey
print*,spread((/5/),1,3)
e
Processing commands for [EMAIL PROTECTED]:
> submitter 319255 debian-x@lists.debian.org
Bug#319255: gcc-4.0: Please Include Fix for GCC Bug 22278
Changed Bug submitter from David Nusinow <[EMAIL PROTECTED]> to [EMAIL
PROTECTED]
> thank you
Stopping processing here.
Please contact me if you need
Package: gcc-4.0
Version: 4.0.1-2
Severity: wishlist
Tags: patch
GCC bug http://gcc.gnu.org/bugzilla/show_bug.cgi?id=22278 causes problems
for the X.Org X server. We currently have a work around in place for the
most noticeable issues, but code potentially displaying this problem is
scattered thro
Your message dated Wed, 20 Jul 2005 12:02:41 -0400
with message-id <[EMAIL PROTECTED]>
and subject line Bug#318535: fixed in gcc272 2.7.2.3-19
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now
Accepted:
gcc272-docs_2.7.2.3-19_all.deb
to pool/main/g/gcc272/gcc272-docs_2.7.2.3-19_all.deb
gcc272_2.7.2.3-19.diff.gz
to pool/main/g/gcc272/gcc272_2.7.2.3-19.diff.gz
gcc272_2.7.2.3-19.dsc
to pool/main/g/gcc272/gcc272_2.7.2.3-19.dsc
gcc272_2.7.2.3-19_i386.deb
to pool/main/g/gcc272/gcc272_
There are disparities between your recently accepted upload and the
override file for the following file(s):
gcc272-docs_2.7.2.3-19_all.deb: package says section is doc, override says
devel.
gcc272-docs_2.7.2.3-19_all.deb: package says priority is optional, override
says extra.
gcc272_2.7.2.3-19
gcc272_2.7.2.3-19_i386.changes uploaded successfully to localhost
along with the files:
gcc272_2.7.2.3-19.dsc
gcc272_2.7.2.3-19.diff.gz
gcc272-docs_2.7.2.3-19_all.deb
gcc272_2.7.2.3-19_i386.deb
Greetings,
Your Debian queue daemon
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
wi
Your message dated Wed, 20 Jul 2005 11:22:40 +0200
with message-id <[EMAIL PROTECTED]>
and subject line [fixed in 3.3] gcc 3.0.4 generates bad code on Debian
3.0/PARISC
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this
Your message dated Wed, 20 Jul 2005 11:24:32 +0200
with message-id <[EMAIL PROTECTED]>
and subject line [fixed in 3.2] gcc bug pr9164 present in stable/Alpha
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the
Your message dated Wed, 20 Jul 2005 11:28:23 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#302033: dpkg-architecture: Specified GNU system type
i386-linux does not match gcc system type i486-linux-gnu
has caused the attached Bug report to be marked as done.
This means that you cl
Your message dated Wed, 20 Jul 2005 10:26:04 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#277845: This seems to be fixed upstream...
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it
Your message dated Wed, 20 Jul 2005 09:43:41 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#315502: gcc-3.3: [sparc] gcc -m64 fails to link binaries
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is
Your message dated Wed, 20 Jul 2005 09:39:11 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Bug#314997: gcc-4.0: fails to be compiled
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is n
Your message dated Wed, 20 Jul 2005 09:06:01 +0200
with message-id <[EMAIL PROTECTED]>
and subject line fixed in recent gcc-4.0 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your res
Your message dated Wed, 20 Jul 2005 09:21:40 +0200
with message-id <[EMAIL PROTECTED]>
and subject line libgcc1 should install into /lib64, not /lib/64
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case i
Your message dated Wed, 20 Jul 2005 09:06:01 +0200
with message-id <[EMAIL PROTECTED]>
and subject line fixed in recent gcc-4.0 upload
has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your res
Processing commands for [EMAIL PROTECTED]:
> tags 188976 + wontfix
Bug#188976: libgcc1 should install into /lib64, not /lib/64
Tags were: woody
Tags added: wontfix
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug tracking system administrator
(administrato
20 matches
Mail list logo
