public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Mike Stump <mikestump@comcast.net>
To: Mike & Elizabeth Stump <mikestump@comcast.net>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
	gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: we are starting the wide int merge
Date: Tue, 06 May 2014 23:16:00 -0000	[thread overview]
Message-ID: <5F27DB78-991E-46E3-AEA3-ED9CBA188268@comcast.net> (raw)
In-Reply-To: <26FAA857-3084-4D75-AE89-3E24ADA98801@comcast.net>

On May 6, 2014, at 3:54 PM, Mike Stump <mikestump@comcast.net> wrote:
> 
> I’m pretty sure this:

> will fix it.  If someone can confirm that would be great.

I tried that on my p7 and on my x86_64 machines, they both build fine.

  parent reply	other threads:[~2014-05-06 23:16 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-06 15:19 Kenneth Zadeck
2014-05-06 19:21 ` Mike Stump
2014-05-06 21:17   ` Jan-Benedict Glaw
2014-05-06 22:54     ` Mike Stump
2014-05-06 23:03       ` Jan-Benedict Glaw
2014-05-06 23:16       ` Mike Stump [this message]
2014-05-06 23:53       ` Mike Stump
2014-05-06 22:59     ` Christophe Lyon
2014-05-07  7:48       ` Andreas Schwab
2014-05-07  9:40         ` Christophe Lyon
2014-05-07  7:07   ` Jan-Benedict Glaw
2014-05-07 10:27     ` Richard Sandiford
2014-05-08 22:48   ` iq2000-elf: wide-int fallout (was: we are starting the wide int merge) Jan-Benedict Glaw
2014-05-08 23:02     ` Oleg Endo
2014-05-08 23:06     ` UTItype fallout (was: wide-int fallout) Jan-Benedict Glaw
2014-05-10 19:42   ` we are starting the wide int merge Gerald Pfeifer
2014-05-16 16:56     ` Gerald Pfeifer
2014-05-17  8:33       ` Richard Sandiford
2014-05-19  3:08         ` Gerald Pfeifer
2014-05-19  6:47           ` Richard Sandiford
2014-05-19 17:33             ` Richard Sandiford

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=5F27DB78-991E-46E3-AEA3-ED9CBA188268@comcast.net \
    --to=mikestump@comcast.net \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jbglaw@lug-owl.de \
    /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).