public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "townsend at astro dot wisc.edu" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug bootstrap/56656] Suffix or operands invalid for 'movq'
Date: Wed, 20 Mar 2013 12:57:00 -0000 [thread overview]
Message-ID: <bug-56656-4-4zm7GBSEIP@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-56656-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=56656
--- Comment #12 from Rich Townsend <townsend at astro dot wisc.edu> 2013-03-20 12:56:53 UTC ---
(In reply to comment #9)
> So I guess an important question is if the "svn-fetched 4.8.0" wasn't actually
> "svn-fetched trunk" instead, Uros' changes have been committed only for 4.9 and
> not on the 4.8 branch.
It was indeed trunk. I wasn't aware that 4.8 is now a proper branch, so I was
still fetching the trunk.
next prev parent reply other threads:[~2013-03-20 12:57 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-56656-4@http.gcc.gnu.org/bugzilla/>
2013-03-20 2:08 ` [Bug libgcc/56656] " pinskia at gcc dot gnu.org
2013-03-20 2:11 ` townsend at astro dot wisc.edu
2013-03-20 2:16 ` pinskia at gcc dot gnu.org
2013-03-20 4:21 ` townsend at astro dot wisc.edu
2013-03-20 7:45 ` ubizjak at gmail dot com
2013-03-20 8:15 ` dominiq at lps dot ens.fr
2013-03-20 8:15 ` dominiq at lps dot ens.fr
2013-03-20 8:19 ` dominiq at lps dot ens.fr
2013-03-20 8:57 ` jakub at gcc dot gnu.org
2013-03-20 9:29 ` ubizjak at gmail dot com
2013-03-20 9:30 ` [Bug bootstrap/56656] " ubizjak at gmail dot com
2013-03-20 9:32 ` ubizjak at gmail dot com
2013-03-20 12:57 ` townsend at astro dot wisc.edu [this message]
2013-03-21 9:39 ` ubizjak at gmail dot com
2013-03-21 9:40 ` ubizjak at gmail dot com
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-56656-4-4zm7GBSEIP@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: 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).