[Bug sanitizer/84250] Symbol collision when using both Address and Undefined Behavior sanitizers (-fsanitize=address,undefined)

2018-02-13 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=84250 --- Comment #3 from Maxim Ostapenko --- (In reply to Martin Liška from comment #2) > Maxim I've just seen your patch: > https://github.com/google/sanitizers/issues/912#issuecomment-363525012 > > Would it be possible to merge a solution to GCC

[Bug sanitizer/81697] Incorrect ASan global variables alignment on arm

2017-12-03 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81697 --- Comment #5 from Maxim Ostapenko --- Fixed on trunk.

[Bug sanitizer/81923] [ASAN] gcc emites wrong odr asan instrumentation for glibc

2017-08-29 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81923 --- Comment #5 from Maxim Ostapenko --- (In reply to Maxim Ostapenko from comment #4) > Created attachment 42071 [details] > Untested fix > > The patch I'm testing now. It works on attached testcase. Yeeks, this patch is wrong, especially for

[Bug sanitizer/81923] [ASAN] gcc emites wrong odr asan instrumentation for glibc

2017-08-29 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81923 --- Comment #4 from Maxim Ostapenko --- Created attachment 42071 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=42071=edit Untested fix The patch I'm testing now. It works on attached testcase.

[Bug sanitizer/81923] [ASAN] gcc emites wrong odr asan instrumentation for glibc

2017-08-28 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81923 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug target/81861] [8.0 Regression] ASan pr64820.c testcase segfaults with LTO and -fstack-protector-strong

2017-08-17 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81861 Maxim Ostapenko changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug lto/81861] [8.0 Regression] ASan pr64820.c testcase segfaults with LTO and -fstack-protector-strong

2017-08-16 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81861 --- Comment #6 from Maxim Ostapenko --- Created attachment 41990 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41990=edit Untested fix The problem is that LTO doesn't propagate changed ix86_stack_protector_guard_reg value: 6654 /*

[Bug tree-optimization/81861] ASan pr64820.c testcase segfaults with LTO and -fstack-protector-strong

2017-08-16 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81861 --- Comment #3 from Maxim Ostapenko --- (In reply to Uroš Bizjak from comment #1) > You didn't specify compile flags, but using: > > -O2 -fstack-protector-strong -fsanitize=address, I get: Sorry, here they are: $

[Bug tree-optimization/81861] New: ASan pr64820.c testcase segfaults with LTO and -fstack-protector-strong

2017-08-16 Thread m.ostapenko at samsung dot com
Priority: P3 Component: tree-optimization Assignee: unassigned at gcc dot gnu.org Reporter: m.ostapenko at samsung dot com CC: ubizjak at gmail dot com Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc

[Bug sanitizer/81697] Incorrect ASan global variables alignment on arm

2017-08-04 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=81697 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug sanitizer/61771] Test failures in ASan testsuite on ARM Linux due to FP format mismatch between libasan and GCC.

2017-07-07 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=61771 Maxim Ostapenko changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug sanitizer/80953] Support libsanitizer on Solaris

2017-06-07 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80953 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug objc/80798] Dynamic stack buffer (alloca) overflow in ObjC compiler.

2017-05-17 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80798 --- Comment #1 from Maxim Ostapenko --- Created attachment 41372 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=41372=edit Trivial fix

[Bug objc/80798] New: Dynamic stack buffer (alloca) overflow in ObjC compiler.

2017-05-17 Thread m.ostapenko at samsung dot com
Priority: P3 Component: objc Assignee: unassigned at gcc dot gnu.org Reporter: m.ostapenko at samsung dot com Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Build: x86_64-pc-linux-gnu Not sure anybody

[Bug sanitizer/80027] ASAN breaks DT_RPATH $ORIGIN in dlopen()

2017-03-15 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80027 --- Comment #4 from Maxim Ostapenko --- (In reply to Michael Thayer from comment #3) > Seems my mistake. I think the ASAN library was still getting loaded > dynamically. Now I have the following problem, which I think means that > code

[Bug sanitizer/80027] ASAN breaks DT_RPATH $ORIGIN in dlopen()

2017-03-13 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=80027 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug sanitizer/78663] [7 Regression] Hundreds of asan failures on x86_64-apple-darwin10 at r243019

2017-02-01 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78663 --- Comment #7 from Maxim Ostapenko --- Created attachment 40646 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40646=edit Fix 2 Iain, could you test the following patch? This one is likely to be applied upstream. As a side note, LLVM

[Bug sanitizer/78663] [7 Regression] Hundreds of asan failures on x86_64-apple-darwin10 at r243019

2017-01-30 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78663 --- Comment #6 from Maxim Ostapenko --- (In reply to Maxim Ostapenko from comment #5) > (In reply to Iain Sandoe from comment #4) > > (In reply to Jakub Jelinek from comment #3) > > > Have you raised this with compiler-rt upstream already? > >

[Bug sanitizer/78663] [7 Regression] Hundreds of asan failures on x86_64-apple-darwin10 at r243019

2017-01-30 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78663 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug lto/79061] [7 Regression][LTO][ASAN] LTO plus ASAN fails with "AddressSanitizer: initialization-order-fiasco"

2017-01-25 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061 --- Comment #28 from Maxim Ostapenko --- (In reply to Jakub Jelinek from comment #27) > I think the problem is in the vnode->dynamically_initialized handling, as > well as in get_translation_unit_decl being totally unreliable. > When LTO merges

[Bug lto/79061] [7 Regression][LTO][ASAN] LTO plus ASAN fails with "AddressSanitizer: initialization-order-fiasco"

2017-01-25 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061 --- Comment #26 from Maxim Ostapenko --- (In reply to Maxim Ostapenko from comment #24) > (In reply to Tobias Burnus from comment #23) > > (In reply to Tobias Burnus from comment #22) > > > As I recently did some incremental builds, I will retry

[Bug lto/79061] [7 Regression][LTO][ASAN] LTO plus ASAN fails with "AddressSanitizer: initialization-order-fiasco"

2017-01-25 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061 --- Comment #24 from Maxim Ostapenko --- (In reply to Tobias Burnus from comment #23) > (In reply to Tobias Burnus from comment #22) > > As I recently did some incremental builds, I will retry it after a full > > bootstrap. > > Didn't make a

[Bug lto/79061] [7 Regression][LTO][ASAN] LTO plus ASAN fails with "AddressSanitizer: initialization-order-fiasco"

2017-01-25 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061 --- Comment #21 from Maxim Ostapenko --- (In reply to Tobias Burnus from comment #20) > Created attachment 40574 [details] > New still failing test case (tar.gz), slightly modifying the previous one > > (In reply to chefmax from comment #19) >

[Bug fortran/79165] 100% compile-time increase for polyhedron aermod by r244581

2017-01-24 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79165 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug lto/79061] [7 Regression][LTO][ASAN] LTO plus ASAN fails with "AddressSanitizer: initialization-order-fiasco"

2017-01-17 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061 --- Comment #14 from Maxim Ostapenko --- (In reply to Richard Biener from comment #13) > (In reply to Maxim Ostapenko from comment #12) > > Created attachment 40525 [details] > > Untested fix 2. > > > > The patch I'm testing now. > >

[Bug lto/79061] [7 Regression][LTO][ASAN] LTO plus ASAN fails with "AddressSanitizer: initialization-order-fiasco"

2017-01-16 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061 Maxim Ostapenko changed: What|Removed |Added Attachment #40514|0 |1 is obsolete|

[Bug lto/79061] [7 Regression][LTO][ASAN] LTO plus ASAN fails with "AddressSanitizer: initialization-order-fiasco"

2017-01-16 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061 --- Comment #11 from Maxim Ostapenko --- (In reply to Maxim Ostapenko from comment #10) > Yeah, but it seems that lto doesn't propagate source location either: > > /* Output info about new location into bitpack BP. >After outputting

[Bug lto/79061] [7 Regression][LTO][ASAN] LTO plus ASAN fails with "AddressSanitizer: initialization-order-fiasco"

2017-01-16 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061 --- Comment #10 from Maxim Ostapenko --- Yeah, but it seems that lto doesn't propagate source location either: /* Output info about new location into bitpack BP. After outputting bitpack, lto_output_location_data has to be done to output

[Bug lto/79061] [7 Regression][LTO][ASAN] LTO plus ASAN fails with "AddressSanitizer: initialization-order-fiasco"

2017-01-16 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061 --- Comment #8 from Maxim Ostapenko --- (In reply to Jakub Jelinek from comment #7) > Comment on attachment 40514 [details] > Untested fix 1. > > But DECL_SOURCE_FILE is not the main input file of the TU that contains it, > if e.g. a variable

[Bug lto/79061] [7 Regression][LTO][ASAN] LTO plus ASAN fails with "AddressSanitizer: initialization-order-fiasco"

2017-01-13 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061 --- Comment #6 from Maxim Ostapenko --- Created attachment 40514 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40514=edit Untested fix 1. The fix I'm testing now. With this patch trivial example works and attached testcase doesn't raise

[Bug lto/79061] [7 Regression][LTO][ASAN] LTO plus ASAN fails with "AddressSanitizer: initialization-order-fiasco"

2017-01-12 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79061 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug lto/79042] LTO doesn't propagate node->dynamically_initialized bit for varpool nodes.

2017-01-12 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=79042 Maxim Ostapenko changed: What|Removed |Added Status|NEW |RESOLVED Resolution|---

[Bug lto/79042] New: LTO doesn't propagate node->dynamically_initialized bit for varpool nodes.

2017-01-10 Thread m.ostapenko at samsung dot com
ity: normal Priority: P3 Component: lto Assignee: unassigned at gcc dot gnu.org Reporter: m.ostapenko at samsung dot com Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Build: x86_64-pc-linux-

[Bug sanitizer/78532] [7 Regression] libsanitizer fails to build on sparc64-linux-gnu

2016-11-30 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78532 --- Comment #7 from Maxim Ostapenko --- Created attachment 40197 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40197=edit Fix Right. Attached patch fixes build error (perhaps all sparc stuff should go upstream, because I think we

[Bug sanitizer/78532] [7 Regression] libsanitizer fails to build on sparc64-linux-gnu

2016-11-30 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78532 --- Comment #6 from Maxim Ostapenko --- (In reply to jos...@codesourcery.com from comment #5) > On Tue, 29 Nov 2016, m.ostapenko at samsung dot com wrote: > > > /home/max/src/glibc/resolv/ns_print.c:99: undefin

[Bug sanitizer/78532] [7 Regression] libsanitizer fails to build on sparc64-linux-gnu

2016-11-29 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78532 --- Comment #3 from Maxim Ostapenko --- (In reply to Matthias Klose from comment #2) > glibc 2.24 and linux 4.8.7. Could you also share how you configure Glibc? Do you use native or cross build? I'm asking because Glibc 2.24 fails to build for

[Bug sanitizer/78532] [7 Regression] libsanitizer fails to build on sparc64-linux-gnu

2016-11-29 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78532 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug sanitizer/78307] [7 Regression] missing symbols in libubsan without changing the soname

2016-11-18 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78307 --- Comment #9 from Maxim Ostapenko --- Can we close this?

[Bug sanitizer/78267] [7 Regression] libsanitizer breaks bootstrap on x86_64-apple-darwin16 at r241977

2016-11-16 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78267 --- Comment #47 from Maxim Ostapenko --- (In reply to r...@cebitec.uni-bielefeld.de from comment #45) > > --- Comment #44 from Maxim Ostapenko --- > [...] > >> Otherwise the definition of SANITIZER_OS_TRACE results in > >>

[Bug sanitizer/78267] [7 Regression] libsanitizer breaks bootstrap on x86_64-apple-darwin16 at r241977

2016-11-15 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78267 --- Comment #44 from Maxim Ostapenko --- (In reply to Jack Howarth from comment #41) > (In reply to r...@cebitec.uni-bielefeld.de from comment #39) > > > --- Comment #36 from Jack Howarth --- > > > Created attachment 40044 [details] > > > -->

[Bug sanitizer/78267] [7 Regression] libsanitizer breaks bootstrap on x86_64-apple-darwin16 at r241977

2016-11-14 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78267 --- Comment #28 from Maxim Ostapenko --- So, perhaps I can commit it (from #15) as Jakub suggested to restore GCC bootstrap for now?

[Bug sanitizer/77827] tsan lacks support for 48 bit VMA on aarch64

2016-11-13 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77827 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug sanitizer/78307] [7 Regression] missing symbols in libubsan without changing the soname

2016-11-11 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78307 --- Comment #6 from Maxim Ostapenko --- (In reply to Jakub Jelinek from comment #5) > (In reply to Maxim Ostapenko from comment #4) > > But LLVM doesn't support shared UBSan runtime (the only one supported is > > ASan) and AFAIK there aren't any

[Bug sanitizer/78307] [7 Regression] missing symbols in libubsan without changing the soname

2016-11-11 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78307 --- Comment #4 from Maxim Ostapenko --- (In reply to Jakub Jelinek from comment #3) > Sure, it doesn't affect gcc emitted code unless somebody calls those > directly, but perhaps say llvm compiled code using the shared libubsan.so. But LLVM

[Bug sanitizer/78307] [7 Regression] missing symbols in libubsan without changing the soname

2016-11-11 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78307 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug sanitizer/78294] -fsanitize=thread broken

2016-11-10 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78294 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug sanitizer/78267] [7 Regression] libsanitizer breaks bootstrap on x86_64-apple-darwin16 at r241977

2016-11-10 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78267 --- Comment #15 from Maxim Ostapenko --- Created attachment 40012 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40012=edit Untested fix 2. Ok, thanks. I'm attaching a second short-term fix for now.

[Bug sanitizer/78267] [7 Regression] libsanitizer breaks bootstrap on x86_64-apple-darwin16 at r241977

2016-11-10 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78267 --- Comment #13 from Maxim Ostapenko --- (In reply to Rainer Orth from comment #11) > (In reply to Jakub Jelinek from comment #5) > > extern char **environ; > > #endif > > > > -#if defined(__has_include) && __has_include() > > +#if

[Bug sanitizer/78267] [7 Regression] libsanitizer breaks bootstrap on x86_64-apple-darwin16 at r241977

2016-11-09 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78267 --- Comment #8 from Maxim Ostapenko --- (In reply to Dominique d'Humieres from comment #7) > > Attaching untested fix. > > Dominique, could you try it? > > Allow for ~2 hours. Or better Jakub's fix, it looks cleaner.

[Bug sanitizer/78267] [7 Regression] libsanitizer breaks bootstrap on x86_64-apple-darwin16 at r241977

2016-11-09 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78267 --- Comment #6 from Maxim Ostapenko --- Created attachment 40007 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=40007=edit Untested fix. Attaching untested fix. Dominique, could you try it?

[Bug sanitizer/78267] [7 Regression] libsanitizer breaks bootstrap on x86_64-apple-darwin16 at r241977

2016-11-09 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78267 --- Comment #4 from Maxim Ostapenko --- (In reply to Iain Sandoe from comment #3) > (In reply to Maxim Ostapenko from comment #1) > > Eh, mine. > > > > typedef void (^os_trace_payload_t)(xpc_object_t xdict) looks very strange, > > it seems that

[Bug sanitizer/78267] [7 Regression] libsanitizer breaks bootstrap on x86_64-apple-darwin16 at r241977

2016-11-08 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78267 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug sanitizer/77982] deadlock in asan thread initialization/interception.

2016-10-26 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77982 --- Comment #11 from Maxim Ostapenko --- Created attachment 39882 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=39882=edit Untested fix Untested fix (works for me with attached testcase). To sum up: 1) dlopen grabs a

[Bug sanitizer/77982] deadlock in asan thread initialization/interception.

2016-10-25 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77982 --- Comment #10 from Maxim Ostapenko --- (In reply to Pawel Sikora from comment #9) > (In reply to Maxim Ostapenko from comment #8) > > > Hm, perhaps environment issue. What version of Glibc do you use? > > glibc-2.23.1-10.fc24.x86_64

[Bug sanitizer/77982] deadlock in asan thread initialization/interception.

2016-10-25 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77982 --- Comment #8 from Maxim Ostapenko --- (In reply to Pawel Sikora from comment #7) > (In reply to Maxim Ostapenko from comment #6) > > The attached testcase works for me with current trunk GCC: > > > > max@max:/tmp/bug$ make > > rm -f m *.so >

[Bug sanitizer/77982] deadlock in asan thread initialization/interception.

2016-10-24 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=77982 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug testsuite/63299] ASan reported alloc-dealloc-mismatch in g++.old-deja/g++.jason/init3.C

2016-09-19 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=63299 Maxim Ostapenko changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug driver/72765] New: Dynamic stack buffer overflow in GCC driver with -save-temps switch.

2016-08-01 Thread m.ostapenko at samsung dot com
Priority: P3 Component: driver Assignee: unassigned at gcc dot gnu.org Reporter: m.ostapenko at samsung dot com Target Milestone: --- Host: x86_64-pc-linux-gnu Target: x86_64-pc-linux-gnu Build: x86_64-pc-linux-gnu When

[Bug sanitizer/71480] ASan should align string constants to shadow granularity.

2016-06-10 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71480 Maxim Ostapenko changed: What|Removed |Added Status|UNCONFIRMED |RESOLVED Resolution|---

[Bug sanitizer/71480] ASan should align string constants to shadow granularity.

2016-06-10 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71480 --- Comment #3 from Maxim Ostapenko --- Thanks, will post the fix in ML soon.

[Bug sanitizer/71480] ASan should align string constants to shadow granularity.

2016-06-09 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71480 --- Comment #1 from Maxim Ostapenko --- The problem appears for arm target only, x86 is fine. $ armv7l-tizen-linux-gnueabi-gcc -v Using built-in specs. COLLECT_GCC=armv7l-tizen-linux-gnueabi-gcc

[Bug sanitizer/71480] New: ASan should align string constants to shadow granularity.

2016-06-09 Thread m.ostapenko at samsung dot com
Priority: P3 Component: sanitizer Assignee: unassigned at gcc dot gnu.org Reporter: m.ostapenko at samsung dot com 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 Target Milestone

[Bug sanitizer/71445] libsanitizer build failure on aarch64-linux-gnu with recent glibc

2016-06-08 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71445 --- Comment #5 from Maxim Ostapenko --- Can we use dlvsym for versioned symbols (recvmsg, sendmsg, etc) in the wrappers?

[Bug sanitizer/71445] libsanitizer build failure on aarch64-linux-gnu with recent glibc

2016-06-07 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71445 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug sanitizer/71291] Firefox with GCC reports stack-buffer-overflow but clang does not

2016-06-01 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71291 --- Comment #13 from Maxim Ostapenko --- Created attachment 38620 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38620=edit mozconfig This .mozconfig with current trunk clang 3.9.0. The source code I've downloaded from here: $ hg clone

[Bug sanitizer/71291] Firefox with GCC reports stack-buffer-overflow but clang does not

2016-05-31 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71291 --- Comment #10 from Maxim Ostapenko --- I've build Firefox locally with clang with optimizations disabled (CFLAGS="-fsanitize=address -fsanitize-recover=address -O0") and got pretty the same backtrace: ==12707==ERROR: AddressSanitizer:

[Bug sanitizer/71291] Firefox with GCC reports stack-buffer-overflow but clang does not

2016-05-31 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=71291 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug sanitizer/70712] False positive from AddressSanitizer with use of 'alignas'

2016-04-22 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70712 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug sanitizer/70624] [6/7 Regression] Several hundred asan failures with 6.0 on x86_64-apple-darwin10.8

2016-04-22 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70624 --- Comment #12 from Maxim Ostapenko --- Should be fixed on trunk and gcc-6-branch. Older branches don't need the patch, because they don't contain 'dyldVersionNumber' in libsanitizer.

[Bug sanitizer/70624] [6 Regression] Several hundred asan failures with 6.0 on x86_64-apple-darwin10.8

2016-04-11 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70624 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug sanitizer/70474] [4.9 Regression] Several hundred asan failures with 4.9.4 on x86_64-apple-darwin15

2016-04-05 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70474 --- Comment #5 from Maxim Ostapenko --- Eh, just forgot about this one, sorry. Will post the patch shortly.

[Bug sanitizer/70541] unnoticed invalid dereference when using address sanitizer

2016-04-05 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70541 --- Comment #4 from Maxim Ostapenko --- (In reply to Jakub Jelinek from comment #3) > (In reply to Maxim Ostapenko from comment #1) > > @@ -2060,7 +2067,20 @@ maybe_instrument_call (gimple_stmt_iterator *iter) > >return true; > > }

[Bug sanitizer/70541] unnoticed invalid dereference when using address sanitizer

2016-04-05 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70541 Maxim Ostapenko changed: What|Removed |Added CC||m.ostapenko at samsung dot com

[Bug sanitizer/70474] [4.9 Regression] Several hundred asan failures with 4.9.4 on x86_64-apple-darwin15

2016-03-31 Thread m.ostapenko at samsung dot com
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=70474 --- Comment #1 from Maxim Ostapenko --- Created attachment 38143 --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=38143=edit Proposed patch. Does this patch fix the problem?