[Bug tree-optimization/29415] [4.2] bad code reordering around inline asm block

2006-10-10 Thread christophe at saout dot de
--- Comment #1 from christophe at saout dot de 2006-10-10 15:40 --- Created an attachment (id=12404) --> (http://gcc.gnu.org/bugzilla/attachment.cgi?id=12404&action=view) preprocessed pthread_mutex_lock.c causing the miscompiled code Call with "gcc -O2 -o test.o -c pthread_mutex_lock.c

[Bug tree-optimization/29415] [4.2] bad code reordering around inline asm block

2006-10-10 Thread pinskia at gcc dot gnu dot org
--- Comment #2 from pinskia at gcc dot gnu dot org 2006-10-10 16:46 --- __asm __volatile ( "call *_dl_sysinfo\n\t" : "=a" (__status) : "0" (240), "b" (&mutex->__data.__lock), "S" (0), "c" (0), "d" (_val), "i" (__builtin_offsetof (tcbhead_t, sysinfo)) : "memory"); I think what you are d

[Bug tree-optimization/29415] [4.2] bad code reordering around inline asm block

2006-10-10 Thread jakub at gcc dot gnu dot org
--- Comment #3 from jakub at gcc dot gnu dot org 2006-10-10 18:55 --- No, that's perfectly valid, you can't jump out of an asm or jump into it, but if you enter the asm and exit it, it doesn't matter what branches or calls were used inside it (of course if the function you call inside it