From: Andreas Jaeger <aj@suse.de>
To: GNU libc hacker <libc-hacker@sources.redhat.com>
Subject: problems with sparc32 build
Date: Wed, 29 Jan 2003 19:56:00 -0000 [thread overview]
Message-ID: <u8r8av687g.fsf@gromit.moeb> (raw)
Building glibc for sparc fails with current CVS with:
In file included from ../linuxthreads/sysdeps/sparc/tls.h:25,
from ../include/tls.h:3,
from ../linuxthreads/internals.h:28,
from ../linuxthreads/sysdeps/pthread/bits/libc-lock.h:27,
from cxa_atexit.c:19:
../linuxthreads/sysdeps/sparc/sparc32/pt-machine.h:59: warning: call-clobbered register used for global register variable
What's going on here? Is my GCC 3.3 CVS version to old? I cannot
find tls patches for sparc in GCC mainline either...
Andreas
--
Andreas Jaeger
SuSE Labs aj@suse.de
private aj@arthur.inka.de
http://www.suse.de/~aj
next reply other threads:[~2003-01-29 19:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-01-29 19:56 Andreas Jaeger [this message]
2003-01-29 21:25 ` Jakub Jelinek
2003-01-29 22:05 ` Thorsten Kukuk
2003-01-30 9:45 ` Jakub Jelinek
2003-01-31 8:15 ` Andreas Jaeger
2003-02-01 11:27 ` Jakub Jelinek
2003-02-02 23:46 ` [PATCH] " Jakub Jelinek
2003-02-04 8:41 ` 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=u8r8av687g.fsf@gromit.moeb \
--to=aj@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).