public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "pinskia at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug optimization/12928] [tree-ssa] Bad assembly code produced when compiling glibc
Date: Thu, 06 Nov 2003 20:48:00 -0000	[thread overview]
Message-ID: <20031106204812.30237.qmail@sources.redhat.com> (raw)
In-Reply-To: <20031106201729.12928.bbooth@redhat.com>

PLEASE REPLY TO gcc-bugzilla@gcc.gnu.org ONLY, *NOT* gcc-bugs@gcc.gnu.org.

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


pinskia at gcc dot gnu dot org changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |UNCONFIRMED
         Resolution|INVALID                     |


------- Additional Comments From pinskia at gcc dot gnu dot org  2003-11-06 20:48 -------
I take that back, I needed to look into the asm a little more:
	bpushl .L__X'$0, $0
	bmovl .L__X'$0, $0
	movl $72, %eax
	int $0x80
	bpopl .L__X'$0, $0

%k2 == $0?


  parent reply	other threads:[~2003-11-06 20:48 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-06 20:17 [Bug optimization/12928] New: " bbooth at redhat dot com
2003-11-06 20:18 ` [Bug optimization/12928] " bbooth at redhat dot com
2003-11-06 20:18 ` bbooth at redhat dot com
2003-11-06 20:28 ` pinskia at gcc dot gnu dot org
2003-11-06 20:38 ` dnovillo at redhat dot com
2003-11-06 20:48 ` pinskia at gcc dot gnu dot org [this message]
2003-11-06 21:05 ` pinskia at gcc dot gnu dot org
2003-11-07 19:45 ` bbooth at redhat dot com
2003-11-07 19:46 ` bbooth at redhat dot com
2003-11-07 19:53 ` pinskia at gcc dot gnu dot org
2004-01-16 20:23 ` rth 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=20031106204812.30237.qmail@sources.redhat.com \
    --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).