public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "revital.eres at linaro dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/48336] Error in generation of ARM ldrd instruction Date: Tue, 29 Mar 2011 15:59:00 -0000 [thread overview] Message-ID: <bug-48336-4-IShsto3ehf@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-48336-4@http.gcc.gnu.org/bugzilla/> http://gcc.gnu.org/bugzilla/show_bug.cgi?id=48336 --- Comment #1 from revital.eres at linaro dot org 2011-03-29 15:43:41 UTC --- Created attachment 23803 --> http://gcc.gnu.org/bugzilla/attachment.cgi?id=23803 A testcase based on simple-object-elf.c Here is the command line for running: /home/revitale/mainline/build/./gcc/xgcc -B/home/revitale/mainline/build/./gcc/ -B/home/revitale/mainline/build/armv7l-unknown-linux-gnueabi/bin/ -B/home/revitale/mainline/build/armv7l-unknown-linux-gnueabi/lib/ -isystem /home/revitale/mainline/build/armv7l-unknown-linux-gnueabi/include -isystem /home/revitale/mainline/build/armv7l-unknown-linux-gnueabi/sys-include -c -DHAVE_CONFIG_H -g -O2 -I. -I../../../gcc/libiberty/../include -W -Wall -Wwrite-strings -Wc++-compat -Wstrict-prototypes -pedantic new_bad.c
next prev parent reply other threads:[~2011-03-29 15:44 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2011-03-29 14:33 [Bug target/48336] New: " revital.eres at linaro dot org 2011-03-29 15:59 ` revital.eres at linaro dot org [this message] 2011-03-30 2:16 ` [Bug target/48336] " vmakarov at gcc dot gnu.org 2011-03-30 8:45 ` rguenth at gcc dot gnu.org 2011-03-30 11:38 ` revital.eres at linaro dot org 2011-03-30 14:51 ` krebbel at gcc dot gnu.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=bug-48336-4-IShsto3ehf@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: linkBe 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).