es, then we think, it's a bug in Compiler. Could you please confirm?
If no, then what is the correct usage of "asm (mfence)" so as to get/ achieve
the memory barrier functionality as expected in the above testcase?
Thanks,
Vivek Kinhekar
Thanks for the quick response, Alexander!
Regards,
Vivek Kinhekar
+91-7709046470
-Original Message-
From: Alexander Monakov
Sent: Friday, April 13, 2018 5:58 PM
To: Vivek Kinhekar
Cc: gcc@gcc.gnu.org
Subject: Re: GCC Compiler Optimization ignores or mistreats MFENCE memory
barrier
# (nil))
fdivrs .LC0# 13*fop_xf_4_i387/1[length = 6]
===
Are we missing anything subtle here?
Regards,
Vivek Kinhekar
-Original Message-
From: Alexander Monakov
Sent: Friday, April 13, 20
Oh! Thanks for the quick response, Jakub.
Regards,
Vivek Kinhekar
-Original Message-
From: Jakub Jelinek
Sent: Friday, April 13, 2018 7:08 PM
To: Vivek Kinhekar
Cc: Alexander Monakov ; gcc@gcc.gnu.org
Subject: Re: GCC Compiler Optimization ignores or mistreats MFENCE memory
barrier
