https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87869
--- Comment #4 from Nick Bowler ---
(In reply to Richard Biener from comment #3)
> I think a better target for optimizing would be the RTL side,
[...]
> I'm sure arc can store to a register address as well.
Yes, if the shortest possible store
: normal
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: nbowler at draconx dot ca
Target Milestone: ---
I happened to notice what appears to be an error in the GCC manual,
ยง6.59.4 ARC Built-in Functions[1]:
Built-in Function: void
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87869
--- Comment #5 from Nick Bowler ---
Looking at some of my other code output, it looks that these long encodings are
emitted a lot more frequently than it would seem they are needed.
If shorter store encodings were used more generally then I'd
Priority: P3
Component: c
Assignee: unassigned at gcc dot gnu.org
Reporter: nbowler at draconx dot ca
Target Milestone: ---
Consider the following code:
% cat >test.c <<'EOF'
#include
void do_stuff_12iter(void)
{
volatile uint32_t *bla
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=87869
--- Comment #1 from Nick Bowler ---
Er, I can't count, the unrolled loop is only ~four times the size.
