public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "hjl.tools at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug sanitizer/59018] [4.9 Regression] libsanitizer doesn't build for x32
Date: Wed, 06 Nov 2013 18:04:00 -0000 [thread overview]
Message-ID: <bug-59018-4-gSZdiZuHoV@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-59018-4@http.gcc.gnu.org/bugzilla/>
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=59018
--- Comment #6 from H.J. Lu <hjl.tools at gmail dot com> ---
(In reply to Kostya Serebryany from comment #4)
> the patches look good and pass our testing on x86_64 and i386.
> Thanks!
> committed as
> http://llvm.org/viewvc/llvm-project?view=revision&revision=194155
> (fixed 4 small lint warnings there)
>
> We have few options:
> 1. I do another full merge, but most likely next week
> 2. You submit these patches directly to gcc now (this may cause a very minor
> headache at the next merge)
My current build has been failing. I'd like to get it fixed as soon
as possible. I will submit my patches to GCC now.
next prev parent reply other threads:[~2013-11-06 18:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-06 10:26 [Bug sanitizer/59018] New: " hjl.tools at gmail dot com
2013-11-06 10:27 ` [Bug sanitizer/59018] " hjl.tools at gmail dot com
2013-11-06 17:48 ` jakub at gcc dot gnu.org
2013-11-06 17:58 ` kcc at gcc dot gnu.org
2013-11-06 18:01 ` kcc at gcc dot gnu.org
2013-11-06 18:04 ` hjl.tools at gmail dot com [this message]
2013-11-06 18:07 ` hjl.tools at gmail dot com
2013-11-06 18:15 ` kcc at gcc dot gnu.org
2013-11-06 21:51 ` hjl at gcc dot gnu.org
2013-11-06 21:52 ` hjl at gcc dot gnu.org
2013-11-06 21:53 ` hjl at gcc dot gnu.org
2013-11-06 21:54 ` hjl at gcc dot gnu.org
2013-11-06 23:54 ` hjl.tools 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-59018-4-gSZdiZuHoV@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).