This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug sanitizer/83388] reference statement index not found error with -fsanitize=null
- From: "rguenth at gcc dot gnu.org" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: Tue, 12 Dec 2017 09:08:30 +0000
- Subject: [Bug sanitizer/83388] reference statement index not found error with -fsanitize=null
- Auto-submitted: auto-generated
- References: <bug-83388-4@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=83388
Richard Biener <rguenth at gcc dot gnu.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Keywords| |lto
CC| |dodji at gcc dot gnu.org,
| |dvyukov at gcc dot gnu.org,
| |jakub at gcc dot gnu.org,
| |kcc at gcc dot gnu.org,
| |rguenth at gcc dot gnu.org
Component|lto |sanitizer
Known to fail| |7.2.1, 8.0
--- Comment #1 from Richard Biener <rguenth at gcc dot gnu.org> ---
If I link with -fsanitize=null it works. I think you can't do without because
otherwise nothing links with libubsan?
The diagnostic might not be too useful though.
I suppose we might be ending up throwing sanitizer stuff on the floor and
getting confused somehow? We do not stream -fsanitize=.. into the lto.opts
section,
thus LTO wrapper doesn't know about it.