public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ian at airs dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/47602] Permit inline asm to clobber PIC register
Date: Fri, 04 Feb 2011 14:16:00 -0000	[thread overview]
Message-ID: <bug-47602-4-5kqiy17Qn8@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-47602-4@http.gcc.gnu.org/bugzilla/>

http://gcc.gnu.org/bugzilla/show_bug.cgi?id=47602

--- Comment #10 from Ian Lance Taylor <ian at airs dot com> 2011-02-04 14:16:32 UTC ---
What advantage do we bring to our users by requiring them to be aware of the
details of the PIC register when writing inline asm code?  Again, those who
*are* aware of the PIC register have complete control.  But many people are
able to write assembler code but have no idea what the PIC register is.  In
what way are we helping them by forcing them to know about it?  How does that
help them write inline assembler which, e.g., uses the cpuid instruction, or
makes a kernel system call which passes a parameter in %ebx?


  parent reply	other threads:[~2011-02-04 14:16 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-02-03 19:40 [Bug rtl-optimization/47602] New: " ian at airs dot com
2011-02-03 19:55 ` [Bug rtl-optimization/47602] " pinskia at gcc dot gnu.org
2011-02-03 23:50 ` ian at airs dot com
2011-02-03 23:52 ` pinskia at gcc dot gnu.org
2011-02-04  0:03 ` [Bug middle-end/47602] " pinskia at gcc dot gnu.org
2011-02-04  0:04 ` pinskia at gcc dot gnu.org
2011-02-04  0:06 ` pinskia at gcc dot gnu.org
2011-02-04  0:08 ` ian at airs dot com
2011-02-04  1:42 ` hjl.tools at gmail dot com
2011-02-04  5:31 ` ian at airs dot com
2011-02-04  8:49 ` ebotcazou at gcc dot gnu.org
2011-02-04 14:16 ` ian at airs dot com [this message]
2011-02-04 14:28 ` schwab@linux-m68k.org
2011-02-04 15:02 ` hjl.tools at gmail dot com
2011-02-04 15:23 ` ebotcazou at gcc dot gnu.org
2011-11-25 20:20 ` pcpa at mandriva dot com.br
2011-12-24 16:38 ` kaffeemonster at googlemail dot com
2014-10-13 17:27 ` kyukhin at gcc dot gnu.org
2015-02-24 20:55 ` law at redhat 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=bug-47602-4-5kqiy17Qn8@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).