public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl dot tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/39139] [4.4 Regression] ICE with stringop and register var
Date: Mon, 09 Feb 2009 20:41:00 -0000 [thread overview]
Message-ID: <20090209204141.29865.qmail@sourceware.org> (raw)
In-Reply-To: <bug-39139-87@http.gcc.gnu.org/bugzilla/>
------- Comment #13 from hjl dot tools at gmail dot com 2009-02-09 20:41 -------
(In reply to comment #10)
> The code in question is setting up parameters for a Xen hypercall. The
> hypercall ABI defines what arguments go in which registers. It uses the
> "register unsigned long arg asm" syntax because that's the only way to specify
> high registers on x86-64.
>
I suspected that is what happened. PR 38925 is another case.
--
hjl dot tools at gmail dot com changed:
What |Removed |Added
----------------------------------------------------------------------------
BugsThisDependsOn| |38925
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=39139
next prev parent reply other threads:[~2009-02-09 20:41 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-09 15:53 [Bug target/39139] New: " jakub at gcc dot gnu dot org
2009-02-09 15:54 ` [Bug target/39139] " jakub at gcc dot gnu dot org
2009-02-09 16:40 ` jakub at gcc dot gnu dot org
2009-02-09 16:45 ` rguenth at gcc dot gnu dot org
2009-02-09 16:53 ` rguenth at gcc dot gnu dot org
2009-02-09 18:12 ` jakub at gcc dot gnu dot org
2009-02-09 19:13 ` hjl dot tools at gmail dot com
2009-02-09 19:39 ` hjl dot tools at gmail dot com
2009-02-09 20:17 ` jakub at gcc dot gnu dot org
2009-02-09 20:29 ` hjl dot tools at gmail dot com
2009-02-09 20:32 ` hjl dot tools at gmail dot com
2009-02-09 20:36 ` jeremy at goop dot org
2009-02-09 20:37 ` jakub at gcc dot gnu dot org
2009-02-09 20:38 ` jeremy at goop dot org
2009-02-09 20:41 ` hjl dot tools at gmail dot com [this message]
2009-02-09 20:43 ` hjl dot tools at gmail dot com
2009-02-09 20:44 ` hjl dot tools at gmail dot com
2009-02-09 20:47 ` hjl dot tools at gmail dot com
2009-02-09 20:49 ` jakub at gcc dot gnu dot org
2009-02-09 20:52 ` hjl dot tools at gmail dot com
2009-02-09 21:01 ` jakub at gcc dot gnu dot org
2009-02-09 21:10 ` hjl dot tools at gmail dot com
2009-02-09 22:37 ` ian at airs dot com
2009-02-10 1:36 ` hjl dot tools at gmail dot com
2009-02-10 9:51 ` bonzini at gnu dot org
2009-02-10 10:21 ` jakub at gcc dot gnu dot org
2009-02-10 10:29 ` jakub at gcc dot gnu dot org
2009-02-10 10:35 ` rguenth at gcc dot gnu dot org
2009-02-10 10:49 ` bonzini at gnu dot org
2009-02-10 16:22 ` jakub at gcc dot gnu dot org
2009-02-10 16:35 ` jakub at gcc dot gnu dot org
[not found] <bug-39139-4@http.gcc.gnu.org/bugzilla/>
2014-06-25 23:48 ` gerald at pfeifer dot com
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=20090209204141.29865.qmail@sourceware.org \
--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).