public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "ubizjak at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug middle-end/33713] [4.3 Regression] can't find a register in class 'GENERAL_REGS' while reloading 'asm'
Date: Wed, 07 Nov 2007 18:56:00 -0000 [thread overview]
Message-ID: <20071107185637.5363.qmail@sourceware.org> (raw)
In-Reply-To: <bug-33713-10053@http.gcc.gnu.org/bugzilla/>
------- Comment #9 from ubizjak at gmail dot com 2007-11-07 18:56 -------
(In reply to comment #8)
> So if we can agree to dump -fforce-addr: yes, please.
Sometimes -fforce-addr produces faster code, as claimed in
http://gcc.gnu.org/ml/fortran/2007-10/msg00048.html
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=33713
next prev parent reply other threads:[~2007-11-07 18:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-09 15:02 [Bug middle-end/33713] New: " rguenth at gcc dot gnu dot org
2007-10-09 16:50 ` [Bug middle-end/33713] " matz at gcc dot gnu dot org
2007-10-09 17:41 ` matz at gcc dot gnu dot org
2007-10-10 6:44 ` bonzini at gnu dot org
2007-10-22 8:36 ` pinskia at gcc dot gnu dot org
2007-10-22 8:49 ` rguenth at gcc dot gnu dot org
2007-11-05 2:47 ` mmitchel at gcc dot gnu dot org
2007-11-06 17:06 ` bonzini at gnu dot org
2007-11-06 21:38 ` rguenther at suse dot de
2007-11-07 16:46 ` matz at gcc dot gnu dot org
2007-11-07 18:56 ` ubizjak at gmail dot com [this message]
2007-11-08 16:32 ` paolo dot bonzini at lu dot unisi dot ch
2007-11-08 19:56 ` bonzini at gnu dot org
2007-11-08 19:58 ` bonzini at gnu dot org
2007-11-10 10:46 ` steven at gcc dot gnu dot org
2007-11-10 13:04 ` bonzini at gnu dot org
2007-11-19 8:54 ` steven at gcc dot gnu dot org
2007-11-19 9:45 ` bonzini at gnu dot org
2007-11-29 11:56 ` aldyh at gcc dot gnu dot org
2007-12-03 23:22 ` aldyh 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=20071107185637.5363.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).