https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
David Malcolm changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #13 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:b7028f060c6760b336b416897412e327ded12ab5
commit r11-3130-gb7028f060c6760b336b416897412e327ded12ab5
Author: David Malcolm
Date: M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #12 from David Malcolm ---
Does r11-2957-gbc62bfb0f43eeada02cb924e3cb5457a399b01c0 fix the failing tests
seen on Darwin?
In any case, I should probably also fix:
> (a) looks like region_model::on_call_pre is erroneously treating a bu
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #11 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:bc62bfb0f43eeada02cb924e3cb5457a399b01c0
commit r11-2957-gbc62bfb0f43eeada02cb924e3cb5457a399b01c0
Author: David Malcolm
Date: M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #10 from CVS Commits ---
The master branch has been updated by David Malcolm :
https://gcc.gnu.org/g:ee7bfbe5eb70a23bbf3a2cedfdcbd2ea1a20c3f2
commit r11-2956-gee7bfbe5eb70a23bbf3a2cedfdcbd2ea1a20c3f2
Author: David Malcolm
Date: M
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #9 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #8)
> (In reply to Iain Sandoe from comment #7)
> > (In reply to David Malcolm from comment #6)
> > > Thanks! The "memset" call has become a call to "__builtin___memset_ch
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #8 from Iain Sandoe ---
(In reply to Iain Sandoe from comment #7)
> (In reply to David Malcolm from comment #6)
> > Thanks! The "memset" call has become a call to "__builtin___memset_chk"
> > (perhaps due to _FORTIFY_SOURCE, or somet
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #7 from Iain Sandoe ---
(In reply to David Malcolm from comment #6)
> Thanks! The "memset" call has become a call to "__builtin___memset_chk"
> (perhaps due to _FORTIFY_SOURCE, or something similar in Darwin's libc?),
(transitive in
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
David Malcolm changed:
What|Removed |Added
Last reconfirmed||2020-08-29
Status|UNCONFIRME
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #5 from Dominique d'Humieres ---
Created attachment 49152
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49152&action=edit
Preprocessed file for the test_5 in memset-1.c
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #4 from Dominique d'Humieres ---
Would it be possible to have a reduced test?
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #3 from David Malcolm ---
Thanks. Unfortunately that didn't trigger the issue for me, sorry.
I'm wondering how best to debug this.
Could you attach the preprocessed source from the testcase(s) please?
Also, if you hack in a call t
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #2 from Dominique d'Humieres ---
> What does the declaration of memset look like in your headers?
> (including attributes)
void*memset(void *__b, int __c, size_t __len);
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=96798
--- Comment #1 from David Malcolm ---
Sorry about the failures.
I attempted to reproduce this via building a cross-compiler with
build==host==x86_64-pc-linux-gnu and --target=x86_64-apple-darwin19.6; I think
this comes down to the tests in quest
14 matches
Mail list logo
