Processing control commands:
> tags -1 + moreinfo
Bug #1063882 [gcc] gcc: Internal error from ternary cond as inline asm parameter
Added tag(s) moreinfo.
--
1063882: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1063882
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
Control: tags -1 + moreinfo
On 14.02.24 02:10, VictorBW wrote:
Package: gcc
Version: 4:12.2.0-3
Severity: normal
X-Debbugs-Cc: knodewaeee+debb...@gmail.com
Dear Maintainer,
I wanted to dynamically select registers for use in an inline assembly
statement, so I tried the questionmark conditiona
On Wed, Nov 11, 2020 at 10:12:19PM +, Dominic Hargreaves wrote:
> During the perl 5.32 transition we observed a build failure on arm64 which
> is reproducible on the porterbox and at lease three different buidds::
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=974073
>
> However Matthi
~((2 * (sizeof(size_t))) -
1)))&& ((old_top)->size& 0x1)&& ((unsigned long)old_end& pagemask) == 0)' failed.
gcc: Internal error: Aborted (program collect2)
Please submit a full bug report.
See for instructions.
I assume a build-depends on gcc-4.3 would be a
;& ((old_top)->size &
0x1) && ((unsigned long)old_end & pagemask) == 0)' failed.
gcc: Internal error: Aborted (program collect2)
Please submit a full bug report.
See for instructions.
I assume a build-depends on gcc-4.3 would be a workaround for this, but
that should
Seemed like the best thing to do was to send it to the Debian list and
have you guys forward it to the GNU list if necessary, since I
couldn't supply some of the things requested by the GNU Bug reporting
protocol (like build configuration options.)
Here you go:
[EMAIL PROTECTED]:~$ cat > hellowor
9:17 -0700
From: Thomas Bushnell BSG <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: gcc: Internal error compiling lilypond on hppa
X-Reply-Permission: Posted or emailed replies to this message constitute
permission for an emailed response.
X-PGP-Fingerprint: 1F0A1E51 63
20:49:17 -0700
From: Thomas Bushnell BSG <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: gcc: Internal error compiling lilypond on hppa
X-Reply-Permission: Posted or emailed replies to this message constitute
permission for an emailed response.
X-PGP-Fingerprint: 1F0A1E51 63
9:17 -0700
From: Thomas Bushnell BSG <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED]
Subject: gcc: Internal error compiling lilypond on hppa
X-Reply-Permission: Posted or emailed replies to this message constitute
permission for an emailed response.
X-PGP-Fingerprint: 1F0A1E51 63
On Sun, Oct 23, 2005 at 12:41:18PM -0700, Thomas Bushnell BSG wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > If the gcc maintainers think that pointing g++ at g++-3.4 on these archs is
> > the best option, I'm game. One disadvantage is that it wouldn't let us get
> > feedback about what
Matthias Klose <[EMAIL PROTECTED]> writes:
>> > ahh, ok. so you did check that defaulting to g++-3.4 on these archs
>> > doesn't reveal another RC bug and we should remove g++-3.4 on these
>> > archs as well?
>>
>> Nope, did you when you told me to downgrade my package to use g++-3.4?
>>
>> I me
Thomas Bushnell BSG writes:
> Matthias Klose <[EMAIL PROTECTED]> writes:
>
> > Thomas Bushnell BSG writes:
> >> Steve Langasek <[EMAIL PROTECTED]> writes:
> >>
> >> > If the gcc maintainers think that pointing g++ at g++-3.4 on these archs
> >> > is
> >> > the best option, I'm game. One disadva
Matthias Klose <[EMAIL PROTECTED]> writes:
> Thomas Bushnell BSG writes:
>> Steve Langasek <[EMAIL PROTECTED]> writes:
>>
>> > If the gcc maintainers think that pointing g++ at g++-3.4 on these archs is
>> > the best option, I'm game. One disadvantage is that it wouldn't let us get
>> > feedback
Thomas Bushnell BSG writes:
> Steve Langasek <[EMAIL PROTECTED]> writes:
>
> > If the gcc maintainers think that pointing g++ at g++-3.4 on these archs is
> > the best option, I'm game. One disadvantage is that it wouldn't let us get
> > feedback about what else might be wrong with g++-4.0 on tho
Steve Langasek <[EMAIL PROTECTED]> writes:
> If the gcc maintainers think that pointing g++ at g++-3.4 on these archs is
> the best option, I'm game. One disadvantage is that it wouldn't let us get
> feedback about what else might be wrong with g++-4.0 on those architectures,
> but we probably al
Processing commands for [EMAIL PROTECTED]:
> tags 335286 - fixed-upstream
Bug#335286: gcc: Internal error compiling lilypond on hppa,arm
Tags were: upstream fixed-upstream
Bug#323133: [PR 21123, 4.0 regression, fixed in 4.1] ICE on arm & m68k when
compiling arts (in cp_expr_size, at cp/c
tags 335286 - fixed-upstream
tags 335286 + help
thanks
Steve Langasek writes:
> On Sat, Oct 22, 2005 at 11:18:00PM -0700, Thomas Bushnell BSG wrote:
> > I find it ludicrous to think that the best solution here is to force a
> > jillion maintainers to workaround the bug and recompile.
>
> I would
On Sat, Oct 22, 2005 at 11:18:00PM -0700, Thomas Bushnell BSG wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > This is the single most common build failure on arm, hppa, and m68k right
> > now, and has affected literally dozens or hundreds of other packages. I
> > do kinda know it on sight
Steve Langasek <[EMAIL PROTECTED]> writes:
> This is the single most common build failure on arm, hppa, and m68k right
> now, and has affected literally dozens or hundreds of other packages. I
> do kinda know it on sight by this point.
>
>> Moreover, this bug should remain filed against gcc-4.0,
Processing commands for [EMAIL PROTECTED]:
> severity 335286 important
Bug#335286: gcc: Internal error compiling lilypond on hppa,arm
Severity set to `important'.
> merge 335286 323133
Bug#323133: [PR 21123, 4.0 regression, fixed in 4.1] ICE on arm & m68k when
compiling arts (
severity 335286 important
merge 335286 323133
thanks
On Sat, Oct 22, 2005 at 09:59:30PM -0700, Thomas Bushnell BSG wrote:
> Steve Langasek <[EMAIL PROTECTED]> writes:
> > reassign 335286 lilypond
> > thanks
> > On Sat, Oct 22, 2005 at 08:49:17PM -0700, Thomas Bushnell BSG wrote:
> >> Compiling l
Processing commands for [EMAIL PROTECTED]:
> reassign 335286 gcc-4.0
Bug#335286: gcc: Internal error compiling lilypond on hppa,arm
Bug reassigned from package `lilypond' to `gcc-4.0'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
Processing commands for [EMAIL PROTECTED]:
> reassign 335286 lilypond
Bug#335286: gcc: Internal error compiling lilypond on hppa,arm
Bug reassigned from package `gcc-4.0' to `lilypond'.
> thanks
Stopping processing here.
Please contact me if you need assistance.
Debian bug
reassign 335286 lilypond
thanks
On Sat, Oct 22, 2005 at 08:49:17PM -0700, Thomas Bushnell BSG wrote:
> Compiling lilypond 2.6.3-7 on hppa, gcc reports an internal error.
> See:
> http:://buildd.debian.org/fetch.php?&pkg=lilypond&ver=2.6.3-7&arch=hppa&stamp=1130038470&file=log&as=raw
> Severity
reassign 335286 gcc-4.0
thanks
Steve Langasek <[EMAIL PROTECTED]> writes:
> reassign 335286 lilypond
> thanks
>
> On Sat, Oct 22, 2005 at 08:49:17PM -0700, Thomas Bushnell BSG wrote:
>
>> Compiling lilypond 2.6.3-7 on hppa, gcc reports an internal error.
>
>> See:
>> http:://buildd.debian.org/fe
Package: gcc-4.0
Version: 4.0.2-2
Severity: serious
Compiling lilypond 2.6.3-7 on hppa, gcc reports an internal error.
See:
http:://buildd.debian.org/fetch.php?&pkg=lilypond&ver=2.6.3-7&arch=hppa&stamp=1130038470&file=log&as=raw
Severity serious because this creates an FTBFS situation for lilyp
>Submitter-Id: net
>Originator:David Walker
>Organization: Private Individual
>Confidential: no
>Synopsis: GCC internal error in preprocessed C code
>Severity: serious
>Priority: medium
>Category: optimization
>Class: ice-on-legal
Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
From: Jason Dorje Short <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gcc: Internal error: Killed
X-Mailer: reportbug 2.53
Date: Wed, 17 Mar 2004 11:30:
Package: gcc-3.3
Version: 1:3.3.3-3
Severity: normal
I was compiling some source when gcc exited. The message it gave was:
gcc: Internal error: Killed (program cc1)
Please submit a full bug report.
See http://gcc.gnu.org/bugs.html> for instructions.
For Debian GNU/Linux specific bugs,
ple
rov <[EMAIL PROTECTED]>
To: Debian Bug Tracking System <[EMAIL PROTECTED]>
Subject: gcc: internal error - cpp0 got fatal signal 11 - cc -O3 poll.c from
perl5.8.0
X-Mailer: reportbug 1.50
Date: Tue, 28 Jan 2003 18:34:43 +0200
Delivered-To: [EMAIL PROTECTED]
X-Spam-Status: No, hi
Package: gcc
Version: 2:2.95.4-14
Severity: important
I was trying to locally build perl5.8.0 from the source.
The compilation bailed out as follows:
cp lib/IO/Seekable.pm ../../lib/IO/Seekable.pm
/home/vassilii/src/perl-5.8.0/miniperl "-I../../lib" "-I../../lib"
../../lib
31 matches
Mail list logo
