From: Uros Bizjak <ubizjak@gmail.com>
To: Ian Lance Taylor <iant@google.com>
Cc: Rainer Orth <ro@cebitec.uni-bielefeld.de>,
gcc-patches@gcc.gnu.org, gofrontend-dev@googlegroups.com
Subject: Re: [RFC PATCH, go]: Port to ALPHA arch - sysinfo.go fixup
Date: Wed, 01 Jun 2011 07:43:00 -0000 [thread overview]
Message-ID: <BANLkTinS3wz9pK7GafDO72B3K4L-U5uu2A@mail.gmail.com> (raw)
In-Reply-To: <mcraae2pwsr.fsf@coign.corp.google.com>
On Tue, May 31, 2011 at 8:08 PM, Ian Lance Taylor <iant@google.com> wrote:
> Uros Bizjak <ubizjak@gmail.com> writes:
>
>> (BTW: Original calculation of Ctime_ns has a cut'n'paste error,
>> stat.Ctime.Nsec should be used instead of stat.Atime.Nsec).
>
> Thanks. Fixed like so. Bootstrapped and ran Go testsuite on
> x86_64-unknown-linux-gnu. Committed to mainline.
Using your latest fixes, I was able to compile libgo on
alphaev68-pc-linux-gnu out of the box, without any additional patches.
One problem remains in the libgo testsuite: certain tests have to be
compiled with -mieee, otherwise FPE is generated for unordered values.
Any suggestions, where -mieee should be placed?
Thanks,
Uros.
next prev parent reply other threads:[~2011-06-01 7:43 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-30 20:48 Uros Bizjak
2011-03-31 8:41 ` Rainer Orth
2011-04-01 23:17 ` Ian Lance Taylor
2011-04-03 18:02 ` Uros Bizjak
2011-04-07 19:15 ` Rainer Orth
2011-04-22 1:31 ` Ian Lance Taylor
2011-05-02 8:28 ` Uros Bizjak
2011-05-02 14:43 ` Ian Lance Taylor
2011-05-31 19:17 ` Ian Lance Taylor
2011-05-31 19:18 ` Ian Lance Taylor
2011-06-01 7:43 ` Uros Bizjak [this message]
2011-06-01 14:37 ` Ian Lance Taylor
2011-06-01 17:03 ` Mike Stump
2011-06-01 17:49 ` Ian Lance Taylor
2011-07-05 17:03 ` Uros Bizjak
2011-07-05 17:19 ` Mike Stump
2011-07-05 17:47 ` Uros Bizjak
2011-07-06 17:12 ` Uros Bizjak
2011-07-06 17:43 ` Ian Lance Taylor
2011-07-06 17:58 ` Uros Bizjak
2011-07-05 20:13 ` Ian Lance Taylor
2011-04-01 23:10 ` Ian Lance Taylor
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=BANLkTinS3wz9pK7GafDO72B3K4L-U5uu2A@mail.gmail.com \
--to=ubizjak@gmail.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=gofrontend-dev@googlegroups.com \
--cc=iant@google.com \
--cc=ro@cebitec.uni-bielefeld.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).