I don't have a problem with it. My home machine is Ubuntu 10.04 so I wouldn't want to go any further than 4.4 yet.
If we're going to start using C++11 features I suggest that we document on the twiki which ones we're using and in what circumstances so that we can be consistent, i.e., if this particular feature is useful in this particular situation, we should consistently use that feature in new code and migrate old code to use it also as we get motivated to do so. This would also be helpful for people who haven't been tracking the standard and aren't aware of what handy new features are available. Steve On Mon, Oct 22, 2012 at 1:56 AM, Andreas Hansson <[email protected]>wrote: > Hi everyone, > > Following up on a statement in my recent review, I would like to hear what > everyone thinks about bumping the minimum version of gcc to 4.4, and always > use the –std=c++0x flag (the c++11 flag was only added in 4.7). > > Obviously, the first point is to make sure we do not make life too > difficult for existing developers, but hopefully gcc 4.4 should not be a > big problem. The stock gcc on RHE5 and Ubuntu 10.04 is 4.4. On OSX, > llvm-gcc causes problems (as it insist on saying it is gcc 4.2.1), but > clang works fine. Are there any platforms out there were you think there > might be issues? > > In terms of the benefits, looking at > http://gcc.gnu.org/projects/cxx0x.html and > http://clang.llvm.org/cxx_status.html, gcc 4.4 would give us auto-typed > variables, decltype, strongly-typed enums and static asserts amongst other > things (all of these are supported already in clang 2.9). Unfortunately > null-pointer constant, range-based for-loops etc will all have to wait > until we can move to 4.6 (all seems to be in line with clang 3.0), which is > probably too much to ask for at this point. > > What do you think? Are there good/bad things I've forgotten? > > Kind regards, > > Andreas > > > -- IMPORTANT NOTICE: The contents of this email and any attachments are > confidential and may also be privileged. If you are not the intended > recipient, please notify the sender immediately and do not disclose the > contents to any other person, use it for any purpose, or store or copy the > information in any medium. Thank you. > > _______________________________________________ > gem5-dev mailing list > [email protected] > http://m5sim.org/mailman/listinfo/gem5-dev > _______________________________________________ gem5-dev mailing list [email protected] http://m5sim.org/mailman/listinfo/gem5-dev
