On Wed, Mar 19, 2003 at 10:01:07AM +0100, Matthias Klose wrote:
[CC ing the other GCC people as well, not debian-gcc, as this started
with private mails. Feel free to move it's over there]
Moved to -gcc. Happy fun multi-posting!
Randolph Chung writes:
tbh hppa would benefit from going to
Category: bootstrap
Synopsis: [linux-mips]: ICE while building libstdc++
Confidential: no
Severity: serious
Priority: medium
Class: ice-on-legal-code
Submitter-Id: net
Originator: [EMAIL PROTECTED]
Release:gcc-ss-20030317
Environment:
linux-mips SGI
Package: g++-3.2
Version: 1:3.2.3-0pre5
Severity: important
The following program is valid C++, but does not compile:
-- snip --
class X {
public:
templateint d
int bar () {return d;}
};
templateint x
int fooo ()
{
return x;
}
templateclass T
void bar (T g)
{
int kk = fooo17(); // OK
this seems to be the lines from the Makefile which cause error
COMPILER_VERSION := $(shell $(CC) --version)
IS_GCC_30 := $(shell if echo $(COMPILER_VERSION) | $(GREP) -q '^3\.0'; then
echo yes; else echo no; fi)
I am in a GREAT hurry and can't provide further detail for now... sorry
--
On Mon, Mar 17, 2003 at 08:37:30PM +0100, Bo Lorentsen wrote:
On Mon, 2003-03-17 at 18:32, Daniel Jacobowitz wrote:
Huh? Is this your own installation of GCC 3.2? Our
i386-linux/bits/atomicity.h contains the atomic operations, not a
single-threaded version.
No, it is not, it is the
Hi Randolph,
I am looking to rebuild gcc-3.3 64bits to rebuild the last kernel 2.4
to
conitnue my investigation about smp(64bits) [which failled to boot on
a
N4000
when compile d with gcc-3.2 get from unofficial-debs].
If you are working on 64-bit, I would advise staying with 3.0.4 for
On Thu, 2003-03-20 at 19:17, Daniel Jacobowitz wrote:
Those operations are atomic for any number of CPUs, so you're looking
in the wrong place.
Ok, I take Your word for it :-), and I will try to look around ones
again to see if I can locate the problem somewhere else. And I will then
try to
Package: libstdc++5
Version: 1:3.2.3-0pre6
Severity: important
Using libstdc++5 on a 386 CPU may cause Illegal instruction (SIGILL).
Starting program: /usr/bin/python2.2
Program received signal SIGILL, Illegal instruction.
[Switching to Thread 16384 (LWP 297)]
0x400d1b7f in
LAST_UPDATED: Sun Mar 16 10:12:05 UTC 2003
Native configuration is sparc-unknown-linux-gnu
=== g++ tests ===
Running target unix
FAIL: g++.law/profile1.C Execution test
XPASS: g++.other/init5.C Execution test
=== g++ Summary ===
# of expected passes
On Thu, Mar 20, 2003 at 05:49:01PM +0100, Luca Andreucci wrote:
this seems to be the lines from the Makefile which cause error
COMPILER_VERSION := $(shell $(CC) --version)
IS_GCC_30 := $(shell if echo $(COMPILER_VERSION) | $(GREP) -q '^3\.0'; then
echo yes; else echo no; fi)
I am in a
10 matches
Mail list logo
