Hi:
Mac OS X has been on gcc 4.0 for a while,
and I'm not aware of any EPICS base problems.
My only issue is with Matlab, which still
defaults to gcc 3.3.
-Kay
On Oct 26, 2006, at 11:30 , Ernest L. Williams Jr. wrote:
On Thu, 2006-10-26 at 09:24 -0600, Jeff Hill wrote:
I have reveived a bundle of patches to EPICS Base 3.14 that
supposedly
fixes (most of) the GCC 4 warnings.
I don't think that we have gcc 4.0 installed here yet. Is it being
provided
with the latest Linux? I just checked and it isn't provided yet by
the
cygwin installer.
The latest enterprise level linux from RedHat does not use GCC4.
======================================================================
============
[williams@dragon cdrom]$ more /etc/redhat-release
Red Hat Enterprise Linux WS release 4 (Nahant Update 4)
[williams@dragon cdrom]$ gcc -v
Reading specs from /usr/lib/gcc/x86_64-redhat-linux/3.4.6/specs
Configured with: ../configure --prefix=/usr --mandir=/usr/share/man --
infodir=/usr/share/info --enable-shared --enable-threads=posix --
disable-checking --with-system-zlib --enable-__cxa_atexit --disable-
libunwind-exceptions --enable-java-awt=gtk --host=x86_64-redhat-linux
Thread model: posix
gcc version 3.4.6 20060404 (Red Hat 3.4.6-3)
======================================================================
===========
However, if you want to claim support for Fedora and other linux
distros
which moved ahead with GCC 4.x, then the warnings should be addressed.
Thanks,
Ernest
I have reveived a bundle of patches to EPICS Base 3.14 that
supposedly
fixes (most of) the GCC 4 warnings.
Do you want me to ...
- commit them after quick review?
- commit them straight away?
- keep them for my own viewing pleasure?
Should I
- create a special branch?
- tag this commit somehow specially?
- commit them to the 3.14 branch only?
- commit them to both 3.14 branch and 3.15 trunk?
I'd like to hear your comments before completely messing things up
(which I'm going to do anyway, be assured).
I am happy for you to commit a fix Ralph. It seems that it would
be a waste
to commit your fix to R3.14 w/o doing a merge of the R3.14 updates
onto the
main trunk also.
Two concerns:
1) We need to be very careful not to add any new bugs to R3.14
2) There is always the peril that, when suppressing compiler
warnings, we
end up sweeping the dust bunnies under the carpet rather than
eradicating
them, and it might be better to have them in site (flagged by
compiler
warnings) as opposed to having them lurk in dark places
(suppressed by casts
etc).
Jeff
-----Original Message-----
From: Ralph Lange [mailto:[email protected]]
Sent: Thursday, October 26, 2006 6:24 AM
To: EPICS Core Talk
Subject: GCC 4 warnings in EPICS Base
Hi all,
I have reveived a bundle of patches to EPICS Base 3.14 that
supposedly
fixes (most of) the GCC 4 warnings.
Do you want me to ...
- commit them after quick review?
- commit them straight away?
- keep them for my own viewing pleasure?
Should I
- create a special branch?
- tag this commit somehow specially?
- commit them to the 3.14 branch only?
- commit them to both 3.14 branch and 3.15 trunk?
I'd like to hear your comments before completely messing things up
(which I'm going to do anyway, be assured).
Cheers,
Ralph
- References:
- RE: GCC 4 warnings in EPICS Base Jeff Hill
- RE: GCC 4 warnings in EPICS Base Ernest L. Williams Jr.
- Navigate by Date:
- Prev:
RE: GCC 4 warnings in EPICS Base Ernest L. Williams Jr.
- Next:
Re: GCC 4 warnings in EPICS Base Andrew Johnson
- Index:
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
- Navigate by Thread:
- Prev:
RE: GCC 4 warnings in EPICS Base Ernest L. Williams Jr.
- Next:
Re: GCC 4 warnings in EPICS Base Andrew Johnson
- Index:
2002
2003
2004
2005
<2006>
2007
2008
2009
2010
2011
2012
2013
2014
2015
2016
2017
2018
2019
2020
2021
2022
2023
2024
|