On Mon, 8 Feb 2010, Will Coleda wrote:
> My question is: is it necessary for us to jump through these hoops?
> Most of the directives in CFLAGS.in are to quiet a noisy build. The
> most complicated turn off optimization in some or all cases. What's
> the bare mininum we need to support here, e.g. is breaking out the
> optimize flag sufficient? Is having a build with no warnings worth
> jumping through hoops for?
Short summary:
The optimzation hoops are necessary -- especially since rakudo's
--gen-parrot option automatically calls --optimize. Without the
optimization hoops, an optimized build will break on gcc/amd64, and
possibly cause non gcc compilers to crash with an out-of-memory error on
the big core ops files.
The warnings hoops are not *necessary*. Even with them, the build is
generally not warning-free. However, given that some mechanism must be in
place to remove the optimization flags for certain files, it would seem to
me to be appropriate to consider whether that mechanism could be
generalized (at only moderate cost) to also remove warnings flags for
certain files.
--
Andy Dougherty [email protected]
_______________________________________________
http://lists.parrot.org/mailman/listinfo/parrot-dev
