public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "Martin dot vGagern at gmx dot net" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/28635]  New: Interaction between different asm statements
Date: Mon, 07 Aug 2006 15:45:00 -0000	[thread overview]
Message-ID: <bug-28635-8905@http.gcc.gnu.org/bugzilla/> (raw)

I was experimenting with the way gcc does register allocation depending on
different flags. I encountered one strange test file where adding a second asm
statement made a first one fail which did work before. Even stranger, when I
have both parts as separate functions before, the combined version compiles as
well. This interdependence between asm statements seems extremely
counterintuitive to me, and might cause difficult to find bugs in larger
projects.

The fact that omitting optimization causes my code to fail even for the version
including the single asm statements makes this bug seem related to bug 11203.
But the behaviour that some code does not compile even with optimizations, and
that adding some functions makes those parts compile as well, are strange
things not mentioned in that bug, so don't be hasty about marking this a
duplicate.

My compiler is a Gentoo build. I know you would love to make me reproduce this
with a plain vanilla compiler, but I beg you to simply compile my attached test
case with your version. If you can't reproduce the bug, I'll happily take this
to the gentoo bugzilla. But I expect the cause rather deep inside the sources,
nothing likely to be changed by some distribution patch set.


-- 
           Summary: Interaction between different asm statements
           Product: gcc
           Version: 4.1.1
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: inline-asm
        AssignedTo: unassigned at gcc dot gnu dot org
        ReportedBy: Martin dot vGagern at gmx dot net
 GCC build triplet: i686-pc-linux-gnu-gcc
  GCC host triplet: i686-pc-linux-gnu-gcc
GCC target triplet: i686-pc-linux-gnu-gcc


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


             reply	other threads:[~2006-08-07 15:45 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-08-07 15:45 Martin dot vGagern at gmx dot net [this message]
2006-08-07 15:49 ` [Bug inline-asm/28635] " Martin dot vGagern at gmx dot net
2006-08-07 15:53 ` [Bug target/28635] " pinskia at gcc dot gnu dot org
2006-08-07 16:02 ` Martin dot vGagern at gmx dot net
2006-08-07 16:14 ` Martin dot vGagern at gmx dot net
2006-09-22  2:24 ` acahalan at gmail dot com
2006-09-22  7:15 ` Martin dot vGagern at gmx dot net
2009-10-03 22:03 ` [Bug libmudflap/28635] " Martin dot vGagern at gmx dot net

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-28635-8905@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).