Processing commands for [EMAIL PROTECTED]:
> tags 405065 + upstream
Bug#405065: gcc-4.1: gcc takes all the memory and crashes with -O2 -ftrapv
There were no tags set.
Tags added: upstream
> forwarded 405065 http://gcc.gnu.org/PR29534
Bug#405065: gcc-4.1: gcc takes all the memory and crashes with
tags 29534 + upstream
forwarded 29534 http://gcc.gnu.org/PR29534
thanks
* Vincent Lefevre <[EMAIL PROTECTED]> [2006-12-30 22:12]:
> I can reproduce the crash on this simple example:
>
> int main (void)
> {
> int i;
> for (i = 31 ; i >= 0 ; i--)
> {
> volatile int x = 0;
> }
>
* dan aronson <[EMAIL PROTECTED]> [2006-12-26 11:32]:
> newdenoise.cc:32: instantiated from here
> MotionSearcher.hh:2444: internal compiler error: in tsubst, at cp/pt.c:7220
This is invalid code. The GCC bug has been fixed in SVN already but
mjpegtools will need to be changed as well. Some in
Processing commands for [EMAIL PROTECTED]:
> tags 404597 + upstream
Bug#404597: gcc-4.1: compiler error in ETCH while compiling mjpeg-tools from
sourceforge
There were no tags set.
Tags added: upstream
> forwarded 404597 http://gcc.gnu.org/PR29729
Bug#404597: gcc-4.1: compiler error in ETCH whil
On 2006-12-30 22:12:07 +0100, Vincent Lefevre wrote:
> I can reproduce the crash on this simple example:
>
> int main (void)
> {
> int i;
> for (i = 31 ; i >= 0 ; i--)
> {
> volatile int x = 0;
> }
> return 0;
> }
>
> $ gcc -O2 -ftrapv -c gcc-bug.c
> gcc-bug.c: In function 'ma
Package: gcc-4.1
Version: 4.1.1-21
Severity: important
I get the following crash when compiling MPFR 2.2.1, and contrary to
what is said, the crash is 100% reproducible.
$ /usr/bin/make
[...]
gcc -DHAVE_INTTYPES_H=1 -DHAVE_STDINT_H=1 -DTIME_WITH_SYS_TIME=1
-DHAVE_STDARG=1 -DHAVE_SYS_TIME_H=1 -D
Processing commands for [EMAIL PROTECTED]:
> # Automatically generated email from bts, devscripts version 2.9.26
> reassign 404739 gss 0.0.18-1
Bug#404739: gss: FTBFS on amd64: segmentation fault.
Bug reassigned from package `gcc' to `gss'.
>
End of message, stopping processing here.
Please cont
Hello, debian GCC maintainers.
I've recently discovered strange gcc behavior:
Summary:
string ' // comment \ ' in C code performs line wrap.
In the attached file (forgive me for archive. i'm afraid
my mailer would eaten needed spaces) source and make:
$ make test
cc main.c -o show_bug
./
8 matches
Mail list logo