Bug 13340 - mono_atomic_load_acquire macro fails to compile in VS2012
Summary: mono_atomic_load_acquire macro fails to compile in VS2012
Alias: None
Product: Runtime
Classification: Mono
Component: General ()
Version: unspecified
Hardware: PC Windows
: --- normal
Target Milestone: ---
Assignee: Bugzilla
Depends on:
Reported: 2013-07-19 09:45 UTC by Cameron Taggart
Modified: 2013-07-20 18:30 UTC (History)
3 users (show)

Is this bug a regression?: ---
Last known good build:

screenshot of fail (28.27 KB, image/png)
2013-07-19 09:46 UTC, Cameron Taggart

Notice (2018-05-24): bugzilla.xamarin.com is now in read-only mode.

Please join us on Visual Studio Developer Community and in the Xamarin and Mono organizations on GitHub to continue tracking issues. Bugzilla will remain available for reference in read-only mode. We will continue to work on open Bugzilla bugs, copy them to the new locations as needed for follow-up, and add the new items under Related Links.

Our sincere thanks to everyone who has contributed on this bug tracker over the years. Thanks also for your understanding as we make these adjustments and improvements for the future.

Please create a new report on GitHub or Developer Community with your current version information, steps to reproduce, and relevant error messages or log files if you are hitting an issue that looks similar to this resolved bug and you do not yet see a matching new report.

Related Links:

Description Cameron Taggart 2013-07-19 09:45:53 UTC
I first logged the bug here in my mono clone:

libmonoruntime fails to compile in Visual Studio 2012. This is trunk/master from mono.

It looks like there was a recent attempt to make stuff compile with msvc.

I also found a stackoverflow question that [talks about this macro](http://stackoverflow.com/questions/17409384/c-variable-assigned-with-return-value-from-scope-block).
Comment 1 Cameron Taggart 2013-07-19 09:46:44 UTC
Created attachment 4382 [details]
screenshot of fail
Comment 2 Zoltan Varga 2013-07-20 00:06:10 UTC
Should be fixed in f8bf28804c215ad95152591cf38c66c5fda7b4dc.
Comment 3 Cameron Taggart 2013-07-20 18:30:08 UTC
Thanks Zoltan! That fix worked. I logged another bug with a fix here: