public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "carlos at redhat dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/60925] [4.9/5 Regression] hppa: can't find a register in class 'R1_REGS' while reloading 'asm'
Date: Mon, 25 May 2015 04:59:00 -0000 [thread overview]
Message-ID: <bug-60925-4-svnvt7jWeM@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-60925-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=60925
Carlos O'Donell <carlos at redhat dot com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |carlos at redhat dot com
--- Comment #13 from Carlos O'Donell <carlos at redhat dot com> ---
For the record I made glibc use %r5 and saved/restored %r1 as required around
the syscall. I also added more clobbers in the event of future changes to the
kernel interface. This works around the "can't find a register in class FOO
while reloading 'asm'" error from the compiler.
The real culprit here is atomic.h in glibc and the asm in question is the
atomic compare and exchange that is being done via the light-weight kernel
syscall.
prev parent reply other threads:[~2015-05-25 4:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-22 19:36 [Bug target/60925] New: [4.9 " aaro.koskinen at iki dot fi
2014-04-22 19:38 ` [Bug target/60925] " aaro.koskinen at iki dot fi
2014-04-22 19:39 ` aaro.koskinen at iki dot fi
2014-04-23 8:41 ` [Bug target/60925] [4.9/4.10 " rguenth at gcc dot gnu.org
2014-05-22 20:25 ` aaro.koskinen at iki dot fi
2014-05-23 18:01 ` aaro.koskinen at iki dot fi
2014-05-25 11:12 ` aaro.koskinen at iki dot fi
2014-05-25 18:31 ` dave.anglin at bell dot net
2014-05-26 11:34 ` carlos at systemhalted dot org
2014-07-16 13:28 ` jakub at gcc dot gnu.org
2014-10-30 10:40 ` [Bug target/60925] [4.9/5 " jakub at gcc dot gnu.org
2014-12-01 11:59 ` rguenth at gcc dot gnu.org
2015-01-21 6:03 ` law at redhat dot com
2015-01-29 14:38 ` law at redhat dot com
2015-05-25 4:59 ` carlos at redhat dot com [this message]
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=bug-60925-4-svnvt7jWeM@http.gcc.gnu.org/bugzilla/ \
--to=gcc-bugzilla@gcc.gnu.org \
--cc=gcc-bugs@gcc.gnu.org \
/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).