public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "stsp at users dot sourceforge dot net" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug inline-asm/23200] [4.0/4.1/4.2 regression] rejects "i"(&var + 1) Date: Thu, 05 Oct 2006 19:29:00 -0000 [thread overview] Message-ID: <20061005192947.20137.qmail@sourceware.org> (raw) In-Reply-To: <bug-23200-11104@http.gcc.gnu.org/bugzilla/> ------- Comment #25 from stsp at users dot sourceforge dot net 2006-10-05 19:29 ------- > "i"(&var) of course can't work with -fpic, I tried it on an x86_64 today, and it seems to work. If I use -m32, then it doesn't. Why? > it would only work at the expense > of text relocations, but those are not allowed on some architectures and > highly undesirable on the rest of architectures. Is this to always keep the .text section r/o? > In position independent code, > &var typically means you need to load that address from global offset table So, as I understand your answer, the relocation at dynamic-link time is not implemented at all (even on the arches where it is possible)? > into a register, and a register of course can't satisfy "i" constraint. Thanks for the hint. It looks like the things like "a"(&var) do work with -fpic, which should be fine for my needs. -- http://gcc.gnu.org/bugzilla/show_bug.cgi?id=23200
next prev parent reply other threads:[~2006-10-05 19:29 UTC|newest] Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top [not found] <bug-23200-11104@http.gcc.gnu.org/bugzilla/> 2005-10-29 15:11 ` [Bug inline-asm/23200] [4.0/4.1 " steven at gcc dot gnu dot org 2005-10-31 4:37 ` mmitchel at gcc dot gnu dot org 2005-11-11 8:59 ` bonzini at gcc dot gnu dot org 2005-11-11 9:00 ` bonzini at gcc dot gnu dot org 2006-01-14 5:50 ` [Bug inline-asm/23200] [4.0/4.1/4.2 " pinskia at gcc dot gnu dot org 2006-01-15 23:15 ` mmitchel at gcc dot gnu dot org 2006-01-15 23:23 ` steven at gcc dot gnu dot org 2006-01-19 19:50 ` amacleod at redhat dot com 2006-02-04 0:16 ` mrs at apple dot com 2006-02-24 0:26 ` mmitchel at gcc dot gnu dot org 2006-02-24 2:17 ` mrs at apple dot com 2006-02-24 2:24 ` mark at codesourcery dot com 2006-05-13 8:27 ` stsp at users dot sourceforge dot net 2006-05-25 2:33 ` mmitchel at gcc dot gnu dot org 2006-10-04 22:20 ` jakub at gcc dot gnu dot org 2006-10-04 22:33 ` amacleod at redhat dot com 2006-10-05 19:29 ` stsp at users dot sourceforge dot net [this message] 2006-12-08 14:32 ` [Bug inline-asm/23200] [4.0/4.1/4.2/4.3 " amacleod at redhat dot com 2007-02-14 9:06 ` mmitchel at gcc dot gnu dot org 2007-03-10 1:36 ` [Bug inline-asm/23200] [4.0/4.1/4.2 " mmitchel at gcc dot gnu dot org 2007-03-10 1:40 ` mmitchel at gcc dot gnu dot org 2007-03-10 1:41 ` [Bug inline-asm/23200] [4.0/4.1/4.2/4.3 " pinskia at gcc dot gnu dot org 2007-03-12 13:11 ` amacleod at redhat dot com 2007-11-22 15:41 ` jakub at gcc dot gnu dot org 2007-11-22 15:53 ` jakub at gcc dot gnu dot org 2007-11-22 17:27 ` stsp at users dot sourceforge dot net 2008-01-16 22:34 ` [Bug inline-asm/23200] [4.1/4.2/4.3 Regression] " rguenth at gcc dot gnu dot org 2008-01-17 19:09 ` stsp at users dot sourceforge dot net 2008-07-04 20:01 ` [Bug inline-asm/23200] [4.1/4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2008-07-05 5:29 ` stsp at users dot sourceforge dot net 2008-07-05 9:41 ` [Bug inline-asm/23200] [4.2/4.3/4.4 " jsm28 at gcc dot gnu dot org 2009-01-25 18:40 ` rguenth at gcc dot gnu dot org 2009-01-26 16:17 ` amacleod at redhat dot com 2009-03-31 18:54 ` [Bug inline-asm/23200] [4.3/4.4/4.5 " jsm28 at gcc dot gnu dot org 2009-08-04 12:30 ` rguenth at gcc dot gnu dot org 2010-05-22 19:00 ` [Bug inline-asm/23200] [4.3/4.4/4.5/4.6 " rguenth at gcc dot gnu dot org 2010-08-18 22:43 ` pinskia at gcc dot gnu dot org
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=20061005192947.20137.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: linkBe 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).