public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jakub at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug tree-optimization/29415] [4.2] bad code reordering around inline asm block
Date: Tue, 10 Oct 2006 18:55:00 -0000	[thread overview]
Message-ID: <20061010185530.6215.qmail@sourceware.org> (raw)
In-Reply-To: <bug-29415-10561@http.gcc.gnu.org/bugzilla/>



------- Comment #3 from jakub at gcc dot gnu dot org  2006-10-10 18:55 -------
No, that's perfectly valid, you can't jump out of an asm or jump into it,
but if you enter the asm and exit it, it doesn't matter what branches or calls
were used inside it (of course if the function you call inside it is written
in C you need to add used attribute to it to make sure it is not optimized
out if it is not otherwise referenced).


-- 


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


  parent reply	other threads:[~2006-10-10 18:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-10 15:38 [Bug tree-optimization/29415] New: " christophe at saout dot de
2006-10-10 15:40 ` [Bug tree-optimization/29415] " christophe at saout dot de
2006-10-10 16:46 ` pinskia at gcc dot gnu dot org
2006-10-10 18:55 ` jakub at gcc dot gnu dot org [this message]
2006-10-11  0:48 ` [Bug middle-end/29415] " pinskia at gcc dot gnu dot org
2006-10-11  0:57 ` [Bug tree-optimization/29415] [4.2 regression] ] " pinskia at gcc dot gnu dot org
2006-10-11  1:05 ` pinskia at gcc dot gnu dot org
2006-10-11  2:35 ` pinskia at gcc dot gnu dot org
2006-10-11  2:37 ` pinskia at gcc dot gnu dot org
2006-10-11  2:43 ` dberlin at gcc dot gnu dot org
2006-10-11  2:46 ` dberlin at gcc dot gnu dot org
2006-10-13 17:18 ` [Bug tree-optimization/29415] [4.2 Regression] " steven at gcc dot gnu dot org
2006-10-13 17:45 ` pinskia at gcc dot gnu dot org
2006-10-13 17:49 ` dberlin at gcc dot gnu dot org
2006-10-15 21:23 ` mmitchel at gcc dot gnu dot org
2006-10-19 23:06 ` dberlin at gcc dot gnu dot org
2006-10-19 23:07 ` dberlin at gcc dot gnu dot org
2007-11-30 15:25 ` cfriedt at visible-assets dot com
2007-11-30 15:27 ` rguenth at gcc dot gnu dot org
2007-11-30 15:48 ` cfriedt at visible-assets 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=20061010185530.6215.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).