https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
Martin Sebor changed:
What|Removed |Added
Resolution|--- |FIXED
Status|NEW
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
--- Comment #16 from CVS Commits ---
The master branch has been updated by Martin Sebor :
https://gcc.gnu.org/g:3072125a40ccfc139a92d44fb3911a8a7186b025
commit r11-5073-g3072125a40ccfc139a92d44fb3911a8a7186b025
Author: Martin Sebor
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
--- Comment #15 from Jan Hubicka ---
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
>
> --- Comment #14 from Martin Sebor ---
> Created attachment 49572
> --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49572=edit
> Patch under
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
>
> --- Comment #14 from Martin Sebor ---
> Created attachment 49572
> --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49572=edit
> Patch under test.
>
> The attached patch avoids the warning on aarch64. Let me finish testing it
> and
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
--- Comment #14 from Martin Sebor ---
Created attachment 49572
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49572=edit
Patch under test.
The attached patch avoids the warning on aarch64. Let me finish testing it and
submit it later
> I agree we should just rename default_is_empty_type to is_empty_type, export
> it, declare in tree.h and use it instead that complicated test. TYPE_EMPTY_P
> isn't something tree-ssa-uninit.c should care about, that is just whether the
> backend decided it will not be passed at all.
OK, perhaps
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
--- Comment #13 from Jan Hubicka ---
> I agree we should just rename default_is_empty_type to is_empty_type, export
> it, declare in tree.h and use it instead that complicated test. TYPE_EMPTY_P
> isn't something tree-ssa-uninit.c should care
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
--- Comment #12 from Jakub Jelinek ---
I agree we should just rename default_is_empty_type to is_empty_type, export
it, declare in tree.h and use it instead that complicated test. TYPE_EMPTY_P
isn't something tree-ssa-uninit.c should care
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
--- Comment #11 from Jan Hubicka ---
> Note i686-linux bootstrap is still broken in r11-5062 - the PR97853 error.
Yes, as discussed earlier (but perhaps lost in other coments) we need
fix for the targetm.calls.empty_record_p (type) divergence.
> Note i686-linux bootstrap is still broken in r11-5062 - the PR97853 error.
Yes, as discussed earlier (but perhaps lost in other coments) we need
fix for the targetm.calls.empty_record_p (type) divergence. It is not
clear to me if simply calling the default implementation instead of the
rather
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
Jakub Jelinek changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
--- Comment #9 from Jan Hubicka ---
Created attachment 49571
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=49571=edit
Warnings building cc1plus with LTO
This is current set of wranings building cc1plus with LTO. there are 66
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
Andreas Schwab changed:
What|Removed |Added
CC||seurer at gcc dot gnu.org
--- Comment
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
--- Comment #7 from CVS Commits ---
The master branch has been updated by Jan Hubicka :
https://gcc.gnu.org/g:0c9687d0daa08c33456210b87e4060d6397ff4d8
commit r11-5060-g0c9687d0daa08c33456210b87e4060d6397ff4d8
Author: Jan Hubicka
Date: Mon
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
--- Comment #6 from Jan Hubicka ---
I remember that first_field was returning non-NULL (perhaps it is derived from
empty base)?
My patch touched nothing on the condition: it just improved the alias analysis.
So while previously we tought that
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
Target Milestone|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
--- Comment #5 from Martin Sebor ---
The warning code considers more that just TYPE_EMPTY_P():
/* Avoid warning about empty types such as structs with no members.
The first_field() test is important for C++ where the predicate
alone
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
--- Comment #4 from Jan Hubicka ---
And to explain why warning does not trigger without modref, it is because we
are not able to disambiguate the variable with another function call (since we
think it escapes)
(gdb) p debug_gimple_stmt
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
Jan Hubicka changed:
What|Removed |Added
CC||msebor at gcc dot gnu.org
--- Comment #3
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
--- Comment #2 from Jan Hubicka ---
Ok, so the warning is triggering when uninitialized memory is passed to
function argument declared as const. This happens here but is false positive
since the parameter is not used at all. This may have
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97840
Jan Hubicka changed:
What|Removed |Added
Ever confirmed|0 |1
Last reconfirmed|
21 matches
Mail list logo
