https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93231
Wilco changed:
What|Removed |Added
Status|NEW |RESOLVED
Resolution|---
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93231
--- Comment #7 from CVS Commits ---
The master branch has been updated by Wilco Dijkstra :
https://gcc.gnu.org/g:bc071d3a951a98284a3f46043afd44c03c123376
commit r10-5986-gbc071d3a951a98284a3f46043afd44c03c123376
Author: Wilco Dijkstra
Date:
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93231
Wilco changed:
What|Removed |Added
Assignee|unassigned at gcc dot gnu.org |wilco at gcc dot gnu.org
--- Comment #6 f
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93231
--- Comment #5 from Jakub Jelinek ---
(In reply to Wilco from comment #4)
> I guess TREE_INT_CST_LOW should fix that. The goal is to support signed and
> unsigned types.
Maybe. Though, perhaps you want to zero extend the constant from the type'
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93231
--- Comment #4 from Wilco ---
(In reply to Jakub Jelinek from comment #0)
> int ctz2 (int x)
> {
> static const char table[32] =
> {
> 0, 1, 28, 2, 29, 14, 24, 3, 30, 22, 20, 15, 25, 17, 4, 8,
> 31, 27, 13, 23, 21, 19, 16, 7, 26
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93231
Richard Biener changed:
What|Removed |Added
Priority|P3 |P1
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93231
--- Comment #3 from Jakub Jelinek ---
Perhaps with the just added native_encode_initializer, rather than having
separate function for CONSTRUCTOR and STRING_CST it might be better to always
native_encode_initializer at certain offset with byte le
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93231
--- Comment #2 from Jakub Jelinek ---
Also, there is no testcase for the string case, nor any non-target specific
testcase that it at least compiles and perhaps with tree dump scan on selected
targets that it recognizes the ctz.
And I don't see a
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=93231
Andrew Pinski changed:
What|Removed |Added
Keywords||ice-on-valid-code
Status|UNC
