public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "mmitchel at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/33932] miscalculation of asm labels with -g3
Date: Sun, 28 Dec 2008 18:43:00 -0000	[thread overview]
Message-ID: <20081228184157.28410.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33932-11104@http.gcc.gnu.org/bugzilla/>



------- Comment #19 from mmitchel at gcc dot gnu dot org  2008-12-28 18:41 -------
I agree with Steven that there are some cases (like -ffunction-sections) where
even popping back from the debug section after generating it doesn't work. 
However, I'm not sure that's a reason not to do it -- reducing the chances for
unexpected behavior is still progress.  This is a real "gotcha".

At the least, we should document the problem shown by this bug before closing
it.  There should be a warning to users that they must explicitly indicate the
section in which they want to place their "asm", by using an appropriate
".section" directive (or equivalent, depending on their choice of assembler and
operating system).  We should also explain whether this is required for local
asms, or only for those occurring at global scope.  That would at least clarify
our intent.


-- 


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


  parent reply	other threads:[~2008-12-28 18:43 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-10-28 18:52 [Bug inline-asm/33932] New: " stsp at users dot sourceforge dot net
2007-10-28 18:56 ` [Bug inline-asm/33932] " stsp at users dot sourceforge dot net
2007-10-28 18:59 ` pinskia at gcc dot gnu dot org
2007-10-28 19:25 ` stsp at users dot sourceforge dot net
2007-10-29 17:50 ` stsp at users dot sourceforge dot net
2008-01-11 21:17 ` stsp at users dot sourceforge dot net
2008-01-11 21:43 ` mmitchel at gcc dot gnu dot org
2008-01-11 23:41 ` stsp at users dot sourceforge dot net
2008-12-28  2:37 ` pinskia at gcc dot gnu dot org
2008-12-28  9:41 ` stsp at users dot sourceforge dot net
2008-12-28 12:21 ` steven at gcc dot gnu dot org
2008-12-28 12:35 ` stsp at users dot sourceforge dot net
2008-12-28 12:53 ` steven at gcc dot gnu dot org
2008-12-28 13:04 ` stsp at users dot sourceforge dot net
2008-12-28 13:05 ` stsp at users dot sourceforge dot net
2008-12-28 13:16 ` steven at gcc dot gnu dot org
2008-12-28 13:24 ` steven at gcc dot gnu dot org
2008-12-28 13:55 ` stsp at users dot sourceforge dot net
2008-12-28 14:04 ` pinskia at gcc dot gnu dot org
2008-12-28 18:43 ` mmitchel at gcc dot gnu dot org [this message]
2008-12-29 12:31 ` bonzini at gnu dot org
2008-12-29 23:07 ` stsp at users dot sourceforge dot net
2008-12-29 23:50 ` mark at codesourcery dot com
2009-06-10 16:33 ` 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=20081228184157.28410.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).