From: Thorsten Kukuk <kukuk@suse.de>
To: libc-hacker@sources.redhat.com
Subject: glibc 2.2 cvs and gcc 3.1 last snapshot on SPARC
Date: Thu, 11 Apr 2002 12:50:00 -0000 [thread overview]
Message-ID: <20020411215053.A6545@suse.de> (raw)
Hi,
I try to compile current glibc 2.2 cvs snapshot with the latest
gcc 3.1 snapshot. It fails with:
../sysdeps/sparc/sparc32/__longjmp.S: Assembler messages:
../sysdeps/sparc/sparc32/__longjmp.S:41: Error: Illegal operands
../sysdeps/sparc/sparc32/__longjmp.S:43: Error: Illegal operands
../sysdeps/sparc/sparc32/__longjmp.S:48: Error: unknown pseudo-op: `.'
../sysdeps/sparc/sparc32/__longjmp.S:50: Error: Illegal operands
../sysdeps/sparc/sparc32/__longjmp.S:52: Error: Illegal operands
../sysdeps/sparc/sparc32/__longjmp.S:55: Error: unknown pseudo-op: `.'
../sysdeps/sparc/sparc32/__longjmp.S:72: Error: unknown pseudo-op: `.'
../sysdeps/sparc/sparc32/__longjmp.S:76: Error: unknown pseudo-op: `.'
Is this a glibc bug or a gcc 3.1 bug?
Thorsten
--
Thorsten Kukuk http://www.suse.de/~kukuk/ kukuk@suse.de
SuSE Linux AG Deutschherrenstr. 15-19 D-90429 Nuernberg
--------------------------------------------------------------------
Key fingerprint = A368 676B 5E1B 3E46 CFCE 2D97 F8FD 4E23 56C6 FB4B
next reply other threads:[~2002-04-11 19:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-11 12:50 Thorsten Kukuk [this message]
2002-04-11 13:25 ` [PATCH] " Jakub Jelinek
2002-04-11 13:43 ` Ulrich Drepper
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20020411215053.A6545@suse.de \
--to=kukuk@suse.de \
--cc=libc-hacker@sources.redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).