public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "rbuergel at web dot de" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug inline-asm/37562] [4.2] -funroll-loops destroys inline asm code for powerpc
Date: Wed, 17 Sep 2008 18:58:00 -0000 [thread overview]
Message-ID: <20080917185704.26760.qmail@sourceware.org> (raw)
In-Reply-To: <bug-37562-15404@http.gcc.gnu.org/bugzilla/>
------- Comment #5 from rbuergel at web dot de 2008-09-17 18:57 -------
Too bad for newbies to ppc asm. :)
But thank you for your explanations
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=37562
next prev parent reply other threads:[~2008-09-17 18:58 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-17 15:43 [Bug inline-asm/37562] New: [4.2] -funroll-loops destroys inline asm code von powerpc rbuergel at web dot de
2008-09-17 15:45 ` [Bug inline-asm/37562] " rbuergel at web dot de
2008-09-17 16:52 ` [Bug inline-asm/37562] New: " Andrew Thomas Pinski
2008-09-17 16:53 ` [Bug inline-asm/37562] [4.2] -funroll-loops destroys inline asm code for powerpc pinskia at gmail dot com
2008-09-17 18:47 ` rbuergel at web dot de
2008-09-17 18:51 ` pinskia at gcc dot gnu dot org
2008-09-17 18:58 ` rbuergel at web dot de [this message]
2008-09-17 19:08 ` pinskia 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=20080917185704.26760.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).