https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118868
Andrew Pinski changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118868
--- Comment #8 from GCC Commits ---
The trunk branch has been updated by Andrew Pinski :
https://gcc.gnu.org/g:e4fb1b435a65f505b0172b4f0213483c3a07adbf
commit r16-599-ge4fb1b435a65f505b0172b4f0213483c3a07adbf
Author: Andrew Pinski
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118868
--- Comment #7 from Andrew Pinski ---
Created attachment 61412
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61412&action=edit
Patch which I am testing for this
This patch just fixes pointer types.
The others will be fixed seperately bec
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118868
--- Comment #6 from Andrew Pinski ---
Reduced testcase:
void *f(void *a) { return __builtin_assoc_barrier(a); }
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118868
--- Comment #5 from Andrew Pinski ---
Created attachment 61411
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=61411&action=edit
testcase
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118868
--- Comment #4 from Andrew Pinski ---
(In reply to Richard Biener from comment #3)
> Hmm, I'm not sure the GIMPLE verification is sensible, I'd have simply
> required compatible types.
Right, I agree; I suspect I missed that PAREN_EXPR is not f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118868
--- Comment #3 from Richard Biener ---
Hmm, I'm not sure the GIMPLE verification is sensible, I'd have simply
required compatible types.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=118868
Andrew Pinski changed:
What|Removed |Added
Status|UNCONFIRMED |ASSIGNED
Assignee|unassigned
