public inbox for gcc-prs@sourceware.org
help / color / mirror / Atom feed
From: Matthias Klose <doko@klose.in-berlin.de>
To: gcc-gnats@gcc.gnu.org, debian-gcc@lists.debian.org
Subject: c/6897: Code produced with -fPIC reserves EBX, but compiles bad __asm__ anyway
Date: Sat, 01 Jun 2002 13:16:00 -0000	[thread overview]
Message-ID: <E17EFC0-0006XZ-00@gate.local> (raw)


>Number:         6897
>Category:       c
>Synopsis:       Code produced with -fPIC reserves EBX, but compiles bad __asm__ anyway
>Confidential:   no
>Severity:       non-critical
>Priority:       low
>Responsible:    unassigned
>State:          open
>Class:          accepts-illegal
>Submitter-Id:   net
>Arrival-Date:   Sat Jun 01 13:16:00 PDT 2002
>Closed-Date:
>Last-Modified:
>Originator:     camm@enhanced.com
>Release:        3.1 (Debian) (Debian unstable)
>Organization:
The Debian Project
>Environment:
System: Debian GNU/Linux (unstable)
Architecture: i686
	
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Installed/Config-files/Unpacked/Failed-config/Half-installed
|/ Err?=(none)/Hold/Reinst-required/X=both-problems (Status,Err: uppercase=bad)
||/ Name           Version        Description
+++-==============-==============-============================================
ii  gcc-3.1        3.1-2          The GNU C compiler.
ii  g++-3.1        3.1-2          The GNU C++ compiler.
ii  libstdc++4     3.1-2          The GNU stdc++ library version 3
ii  libstdc++4-dev 3.1-2          The GNU stdc++ library version 3 (developmen
ii  binutils       2.12.90.0.7-1  The GNU assembler, linker and binary utiliti
ii  libc6          2.2.5-6        GNU C Library: Shared libraries and Timezone
host: i386-linux
configured with: /mnt/data/gcc-3.1/gcc-3.1-3.1ds2/src/configure -v --enable-languages=c,c++,java,f77,proto,objc,ada --prefix=/usr --mandir=$\(prefix\)/share/man --infodir=$\(prefix\)/share/info --with-gxx-include-dir=$\(prefix\)/include/g++-v3-3.1 --enable-shared --with-system-zlib --enable-long-long --enable-nls --without-included-gettext --enable-clocale=gnu --enable-threads=posix --enable-java-gc=boehm --enable-objc-gc i386-linux
>Description:
[ Reported to the Debian BTS as report #73065.
  Please CC 73065@bugs.debian.org on replies.
  Log of report can be found at http://bugs.debian.org/73065 ]

According to the bug submitter, both files should fail to compile with
the same warning. He has produced verifiably incorrect asm code using
the latter syntax. Rechecked with gcc-3.1.

intech20:/tmp$ cat foo.c
int
main(int argc,char * argv[]) {

  int i=0;

  __asm__ __volatile__ ("addl $1,%%ebx\n\t" : : "b" (i));

}
intech20:/tmp$ cc -fPIC foo.c -o foo
foo.c: In function `main':
foo.c:6: Invalid `asm' statement:
foo.c:6: fixed or forbidden register 3 (bx) was spilled for class BREG.
intech20:/tmp$ cat foo1.c
int
main(int argc,char * argv[]) {

  int i=0;

  __asm__ __volatile__ ("addl $1,%%ebx\n\t" : : "a" (i) : "ebx");

}
intech20:/tmp$ cc -fPIC foo1.c -o foo
intech20:/tmp$ 
>How-To-Repeat:
	
>Fix:
	
>Release-Note:
>Audit-Trail:
>Unformatted:


             reply	other threads:[~2002-06-01 20:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-06-01 13:16 Matthias Klose [this message]
2002-12-19  9:25 ebotcazou

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=E17EFC0-0006XZ-00@gate.local \
    --to=doko@klose.in-berlin.de \
    --cc=73065@bugs.debian.org \
    --cc=debian-gcc@lists.debian.org \
    --cc=gcc-gnats@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).