From: Palmer Dabbelt <palmer@dabbelt.com>
To: joseph@codesourcery.com
To: rep.dot.nop@gmail.com
Cc: gcc-patches@gcc.gnu.org
Cc: Andrew Waterman <andrew@sifive.com>
Cc: kito.cheng@gmail.com
Subject: Re: [PATCH 4/6] RISC-V Port: libsanitizer
Date: Tue, 17 Jan 2017 05:40:00 -0000 [thread overview]
Message-ID: <mhng-98ae6902-6a29-4be6-a72f-43cefe5ef1ab@palmer-mbp2014> (raw)
In-Reply-To: <alpine.DEB.2.20.1701122338340.12673@digraph.polyomino.org.uk>
On Thu, 12 Jan 2017 15:39:54 PST (-0800), joseph@codesourcery.com wrote:
> Have these changes been sent upstream? Although at the present
> development stage applying selected changes might be better than a bulk
> merge from upstream libsanitizer, they should still go upstream so they
> aren't a local patch at the time of the next merge.
Sorry, I didn't know there was an upstream to this. I went to send this
upstream to the LLVM compiler-rt repo, but I think this port is actually
broken: it turns out we hadn't built it in a while (which is why the double-&&
wasn't noticed, it must have come from a rebase) and it looks like we don't
quite have a sane set of Linux headers right now so we don't quite match up
with the SANITIZER_USES_CANONICAL_LINUX_SYSCALLS macro any more.
I think it'd be best if we just drop this for now and wait for our Linux port
to stabilize a bit (which we're planning on doing after the GCC code reviews).
There's a bit too much stuff in flight for me to be able to keep track of it
all right now.
Sorry!
Also, thanks for finding the "&& &&" bug -- I hadn't noticed we weren't
compiling libsanitizer any more.
next prev parent reply other threads:[~2017-01-17 5:40 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-12 2:35 New Port for RISC-V Palmer Dabbelt
2017-01-12 2:35 ` [PATCH 5/6] RISC-V Port: libatomic Palmer Dabbelt
2017-01-12 2:35 ` [PATCH 1/6] RISC-V Port: gcc/config/riscv/riscv.c Palmer Dabbelt
2017-01-12 21:38 ` Joseph Myers
2017-01-16 23:08 ` Andrew Waterman
2017-01-21 5:22 ` Richard Henderson
2017-01-31 1:10 ` Andrew Waterman
2017-01-31 18:07 ` Richard Henderson
2017-01-31 22:33 ` Andrew Waterman
2017-01-12 2:36 ` [PATCH 2/6] RISC-V Port: gcc Palmer Dabbelt
2017-01-12 22:30 ` Joseph Myers
2017-01-13 19:59 ` Andrew Waterman
2017-01-14 10:05 ` Karsten Merker
2017-01-15 0:01 ` Joseph Myers
2017-01-17 5:41 ` Palmer Dabbelt
2017-01-17 20:59 ` Karsten Merker
2017-01-17 21:17 ` Andrew Waterman
2017-01-21 6:53 ` Richard Henderson
2017-01-21 6:45 ` Richard Henderson
2017-01-31 1:21 ` Andrew Waterman
2017-01-31 18:35 ` Richard Henderson
2017-01-31 21:15 ` Andrew Waterman
2017-01-12 2:36 ` [PATCH 4/6] RISC-V Port: libsanitizer Palmer Dabbelt
2017-01-12 23:40 ` Joseph Myers
2017-01-17 5:40 ` Palmer Dabbelt [this message]
2017-01-13 17:23 ` Bernhard Reutner-Fischer
2017-01-12 2:36 ` [PATCH 3/6] RISC-V Port: libgcc Palmer Dabbelt
2017-01-12 23:30 ` Joseph Myers
2017-01-13 7:34 ` Andrew Waterman
2017-01-21 7:09 ` Richard Henderson
2017-01-24 20:30 ` Andrew Waterman
2017-01-12 2:36 ` [PATCH 6/6] RISC-V Port: gcc/testsuite Palmer Dabbelt
2017-01-12 23:43 ` Joseph Myers
2017-01-13 2:34 ` Andrew Waterman
2017-01-12 17:30 ` New Port for RISC-V Joseph Myers
2017-01-12 20:43 ` Andrew Waterman
2017-02-02 9:05 ` New Port for RISC-V v2 Palmer Dabbelt
2017-02-02 9:05 ` [PATCH 4/6] RISC-V Port: libatomic Palmer Dabbelt
2017-02-02 9:05 ` [PATCH 5/6] RISC-V Port: gcc/testsuite Palmer Dabbelt
2017-02-02 9:05 ` [PATCH 3/6] RISC-V Port: libgcc Palmer Dabbelt
2017-02-02 9:06 ` [PATCH 6/6] RISC-V Port: contrib Palmer Dabbelt
2017-02-02 9:06 ` [PATCH 1/6] RISC-V Port: gcc/config/riscv/riscv.c Palmer Dabbelt
2017-02-02 9:06 ` [PATCH 2/6] RISC-V Port: gcc Palmer Dabbelt
2017-02-02 19:07 ` Joseph Myers
2017-02-03 1:08 ` Palmer Dabbelt
2017-02-02 19:18 ` Karsten Merker
2017-02-03 1:08 ` Palmer Dabbelt
2017-02-06 5:36 ` Sandra Loosemore
2017-02-06 18:22 ` Palmer Dabbelt
2017-02-02 19:07 ` New Port for RISC-V v2 Joseph Myers
2017-02-03 1:08 ` Palmer Dabbelt
2017-02-03 20:49 ` Palmer Dabbelt
2017-02-03 21:55 ` Gerald Pfeifer
2017-02-02 21:07 ` Gerald Pfeifer
2017-02-03 1:08 ` Palmer Dabbelt
2017-02-03 7:35 ` Gerald Pfeifer
2017-02-05 18:38 ` New Port for RISC-V v3 Palmer Dabbelt
2017-02-05 18:38 ` [PATCH 4/6] RISC-V Port: libatomic Palmer Dabbelt
2017-02-05 18:39 ` [PATCH 6/6] RISC-V Port: contrib Palmer Dabbelt
2017-02-05 18:39 ` [PATCH 5/6] RISC-V Port: gcc/testsuite Palmer Dabbelt
2017-02-05 18:39 ` [PATCH 3/6] RISC-V Port: libgcc Palmer Dabbelt
2017-02-05 18:39 ` [PATCH 1/6] RISC-V Port: gcc/config/riscv/riscv.c Palmer Dabbelt
2017-02-06 8:21 ` New Port for RISC-V v3 Jakub Jelinek
2017-02-06 19:18 ` Palmer Dabbelt
2017-02-06 19:20 ` Jakub Jelinek
2017-02-06 21:41 ` Palmer Dabbelt
2017-02-08 8:43 ` Eric Botcazou
2017-02-08 18:56 ` [PATCH] Add RISC-V Maintainers Palmer Dabbelt
2017-03-19 9:19 ` Kito Cheng
2017-03-20 16:24 ` Palmer Dabbelt
2017-02-08 18:56 ` New Port for RISC-V v3 Palmer Dabbelt
2017-02-08 18:56 ` [PATCH] Add the RISC-V ELF targets to config-list.mk Palmer Dabbelt
2017-02-06 18:54 ` Mising Patch #2 from the RISC-V v3 Submission Palmer Dabbelt
2017-02-06 19:15 ` Palmer Dabbelt
2018-02-12 11:23 ` Andreas Schwab
2018-02-12 21:53 ` Joseph Myers
2018-02-12 23:18 ` Jim Wilson
2018-02-13 10:35 ` Andreas Schwab
2018-02-15 23:48 ` Palmer Dabbelt
2018-02-20 11:11 ` Andreas Schwab
2018-02-26 10:07 ` Andreas Schwab
2017-02-06 5:11 ` New Port for RISC-V v2 Richard Henderson
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=mhng-98ae6902-6a29-4be6-a72f-43cefe5ef1ab@palmer-mbp2014 \
--to=palmer@dabbelt.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=joseph@codesourcery.com \
/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).