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/33932] miscalculation of asm labels with -g3
Date: Fri, 11 Jan 2008 23:41:00 -0000	[thread overview]
Message-ID: <20080111220235.31689.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33932-11104@http.gcc.gnu.org/bugzilla/>



------- Comment #7 from stsp at users dot sourceforge dot net  2008-01-11 22:02 -------
Thank you for the prompt reply!

I also think simply changing to the previous
section is the good fix because the main problem,
as I see it, is that the -g3 currently has the
different behaveour than the other -gX options.
The fact that asm() doesn't automatically
change to .text is, as you say, not really a bug.
But the erratic behaveour of -g3 certainly is.
I guess the problem is that currently it is not
officially documented what section is used by default,
so the one may say any random section is OK. But IMHO
it would be much better to have a particular section
be a default, and have it documented.


-- 


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


  parent reply	other threads:[~2008-01-11 22:03 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 [this message]
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
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=20080111220235.31689.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).