In general, yes.
But: This is really compiler dependent.
A better approach would be to go through the code base, and rework the problematic code,
step by step.
And when this is done, have a look if there are „volatile“ missing,
and/or if we need better support for multi-core, like synchronizing the L2 caches
on some ARM platforms.
(But I’m not sure, if anybody is running EPICS on this kind of hardware)
It may be good enough to enable it for gcc, if version >= 5.
And what about clang ?
/Torsten
Am 15.03.2016 um 19:08 schrieb Andrew Johnson <[email protected]>:
> http://blog.regehr.org/archives/1307
>
> Should we add the -fno-strict-aliasing flag to the EPICS build rules?
>
> - Andrew
- Replies:
- Re: Strict aliasing blog-post Johnson, Andrew N.
- Re: Strict aliasing blog-post Michael Davidsaver
- Re: Strict aliasing blog-post Michael Davidsaver
- References:
- Strict aliasing blog-post Andrew Johnson
- Navigate by Date:
- Prev:
Strict aliasing blog-post Andrew Johnson
- Next:
Re: Strict aliasing blog-post Johnson, Andrew N.
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
2025
- Navigate by Thread:
- Prev:
Strict aliasing blog-post Andrew Johnson
- Next:
Re: Strict aliasing blog-post Johnson, Andrew N.
- Index:
2002
2003
2004
2005
2006
2007
2008
2009
2010
2011
2012
2013
2014
2015
<2016>
2017
2018
2019
2020
2021
2022
2023
2024
2025
|