https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #24 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:c9ee9c1e3553247c776f33eb0fe0aadee094a192
commit r11-6500-gc9ee9c1e3553247c776f33eb0fe0aadee094a192
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
Richard Biener changed:
What|Removed |Added
Resolution|--- |FIXED
Status|ASSIGNED
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #22 from CVS Commits ---
The master branch has been updated by Richard Biener :
https://gcc.gnu.org/g:fa4a8b6463e0dbc2a072fca835d28ae7a57849d5
commit r11-5925-gfa4a8b6463e0dbc2a072fca835d28ae7a57849d5
Author: Richard Biener
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
Richard Biener changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |rguenth at gcc dot
gnu.org
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #20 from Eric Botcazou ---
> So I'm going to look at this again. Some random thoughts on the Ada bools
> though. It would be nice if the Ada FE could leave boolean_type_node
> untouched so that when the middle-end produces a compare
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #19 from Richard Biener ---
So I'm going to look at this again. Some random thoughts on the Ada bools
though. It would be nice if the Ada FE could leave boolean_type_node
untouched so that when the middle-end produces a compare to f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
Martin Liška changed:
What|Removed |Added
CC||doko at debian dot org
--- Comment #18 fr
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
Richard Biener changed:
What|Removed |Added
CC||jakub at gcc dot gnu.org
--- Comment #1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #16 from Richard Biener ---
(In reply to Richard Biener from comment #15)
> The patch causes g++.dg/vect/simd-bool-comparison-1.cc to FAIL because
> it will result in signed BOOLEAN_TYPEs with precision 1 rejected. Those we
> use for
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #15 from Richard Biener ---
The patch causes g++.dg/vect/simd-bool-comparison-1.cc to FAIL because
it will result in signed BOOLEAN_TYPEs with precision 1 rejected. Those we
use for build_nonstandard_boolean_type via
#0 0x0
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #14 from Martin Liška ---
> Yes, it works. I've been using it for some time in out gcc11 package.
PING
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #13 from Martin Liška ---
(In reply to Richard Biener from comment #12)
> (In reply to Martin Liška from comment #11)
> > Is there any progress about this PR? It's still blocking Ada bootstrap.
>
> Can you check the patch from commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #12 from Richard Biener ---
(In reply to Martin Liška from comment #11)
> Is there any progress about this PR? It's still blocking Ada bootstrap.
Can you check the patch from comment#6? I'm not 100% sure it's correct
but it can at m
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #11 from Martin Liška ---
Is there any progress about this PR? It's still blocking Ada bootstrap.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #10 from Eric Botcazou ---
> Yeah, that was for vector components. Not that I like it much. Can
> the middle-end assume that the Ada boolean types only contain 0 or 1
> or are there other values that are supposed to be well-defined
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #9 from rguenther at suse dot de ---
On Tue, 9 Jun 2020, ebotcazou at gcc dot gnu.org wrote:
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
>
> --- Comment #8 from Eric Botcazou ---
> Well, the middle-end provides build_nonst
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #8 from Eric Botcazou ---
Well, the middle-end provides build_nonstandard_boolean_type to build boolean
types with arbitrary precision so it cannot assume they have precision 1.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #7 from Richard Biener ---
So Ada does
/* In Ada, we use an unsigned 8-bit type for the default boolean type. */
boolean_type_node = make_unsigned_type (8);
TREE_SET_CODE (boolean_type_node, BOOLEAN_TYPE);
but somehow in lto1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
Richard Biener changed:
What|Removed |Added
CC||ebotcazou at gcc dot gnu.org
--- Commen
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #5 from Martin Liška ---
The problematic STMT is:
(gdb) p debug_gimple_stmt(orig_stmt_info->stmt)
_22 = (boolean) _21;
which comes from:
(gdb) p debug_bb(bb)
[count: 0]:
_8 ={v} __gnat_dir_separator;
# DEBUG SR.1076 => _8
_9 ={v} _
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
--- Comment #4 from Martin Liška ---
Created attachment 48711
--> https://gcc.gnu.org/bugzilla/attachment.cgi?id=48711&action=edit
Reproducer LTO bytecode
I think it would be easy to reproduce by LTO LTRANS .o file:
$ git co f8ca4dd657f767c5f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
Martin Liška changed:
What|Removed |Added
Keywords|needs-bisection |
--- Comment #3 from Martin Liška ---
St
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
Martin Liška changed:
What|Removed |Added
Keywords||needs-bisection
Last reconfirmed|
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=95582
Richard Biener changed:
What|Removed |Added
Target Milestone|--- |11.0
Priority|P3
24 matches
Mail list logo
