| 2002 2003 2004 2005 2006 2007 2008 2009 2010 <2011> 2012 2013 2014 2015 2016 2017 2018 2019 2020 2021 2022 2023 2024 2025 | 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 |
| <== Date ==> | <== Thread ==> |
|---|
| Subject: | Re: [Merge] lp:~epics-core/epics-base/epicsR3.15-atomics into lp:epics-base |
| From: | Jeff Hill <[email protected]> |
| To: | Jeff Hill <[email protected]> |
| Date: | Thu, 11 Aug 2011 15:06:35 -0000 |
> Unfortunately -march=i586 sets both a minimum and maximum. So I did hear this comment. To clarify, I will elaborate on your concern. If its true that certain Linux distros include a gcc defaulting to other than 386 (I have only looked at RHEL which includes a gcc defaulting to 386) then I agree that our setting it to i586 could be a negative in the future if the local system defaults to some ubiquitous platform with more capabilities such as pentium-II. So if its true that Linux platforms include a gcc that defaults its arch to some more capable processor then perhaps I should remove the -march=i586 but then I fear that at least some of the (RHEL) linux users will be much less likely to see any benefits from the atomics given the current state of how the build system works. -- https://code.launchpad.net/~epics-core/epics-base/epicsR3.15-atomics/+merge/70642 Your team EPICS Core Developers is requested to review the proposed merge of lp:~epics-core/epics-base/epicsR3.15-atomics into lp:epics-base.