http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57813
--- Comment #8 from Daniel Oertwig ---
Ok, so: Is this behaviour "part" of the language or a bug in gcc?
I could not find any documentation specifying that a sequence point should be
inbetween the (side-effect) evaluation of the function call and
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57813
--- Comment #5 from Daniel Oertwig ---
(In reply to Andrew Pinski from comment #3)
> taskInfo.ready[priority]->wakeTime = Task_enforceTimeslice(priority);
>
> This is the same as:
> (*taskInfo.ready[priority]).wakeTime = Task_enforceT
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57813
Daniel Oertwig changed:
What|Removed |Added
Status|RESOLVED|UNCONFIRMED
Resolution|INVALID
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57813
--- Comment #2 from Daniel Oertwig ---
Oh, I am compiling with:
CFLAGS :=
CFLAGS += -Os
CFLAGS += -funsigned-char
CFLAGS += -funsigned-bitfields
CFLAGS += -fpack-struct
CFLAGS += -fshort-enums
CFLAGS += -ffreestanding
CFLAGS += -Wall -Wextra
CFL
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57813
--- Comment #1 from Daniel Oertwig ---
Created attachment 30451
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30451&action=edit
Disassembly of the relating parts (from *.elf file, i.e. after linking)
Assignee: unassigned at gcc dot gnu.org
Reporter: daniel.oertwig at gmail dot com
Target: avr51
Created attachment 30450
--> http://gcc.gnu.org/bugzilla/attachment.cgi?id=30450&action=edit
Source code relating to the problem
Hi, I assume this to be a bug in how the c
