http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58405
--- Comment #2 from semicontinuity at yandex dot ru ---
Now I cannot reproduce that as well..
It seems that I've compiled it with -ffixed-r30 -ffixed-r31 (different from
original intention) - in this case it produces this kind of assembly .
Still
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58390
--- Comment #2 from semicontinuity at yandex dot ru ---
Agreed, this is probably not a bug but an RFE, can it be re-opened?
movw + ijmp in this case would be faster and shorter, and would not use stack
memory.
Regarding reservation of z - I'm
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=58391
--- Comment #2 from semicontinuity at yandex dot ru ---
Currently, the logic is that if the function contains computed goto, it cannot
be inlined.
My suggestion is to inline the function if
- it is static and used only once in the compilation unit
Assignee: unassigned at gcc dot gnu.org
Reporter: semicontinuity at yandex dot ru
The following code
//
-
static void test(void) {
char flag = 1;
static void* address = L0;
goto *address
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: semicontinuity at yandex dot ru
Trying to speed up the following code, I've placed 'address' variable to the
r2:r3 (and added -ffixed-r2 -ffixed-r3
Priority: P3
Component: target
Assignee: unassigned at gcc dot gnu.org
Reporter: semicontinuity at yandex dot ru
Certain functions with computed goto could be inlined.
Currently, if a function contains computed goto it is not inlined.
Here, the function
