This is the mail archive of the gcc-patches@gcc.gnu.org mailing list for the GCC project.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
Other format: | [Raw text] |
In message <1074551138.25137.159.camel@frodo.toronto.redhat.com>, Diego Novillo
writes:On Mon, 2004-01-19 at 17:12, Dale Johannesen wrote:Yea, let's make this a --param. Cleaning up this kind of thing is actuallyThis adds a new flag, -fuse-global-var, to control whether the .GLOBAL_VAR mechanism is used or not. The default is unchanged. Two reasons: - enable best code gen when the user is willing to accept slow compilation (e.g. benchmarking) - permit construction of small testcases for bugs dependent on .GLOBAL_VAR being used Bootstrapped and tested on Darwin.
I don't think this is a good idea. Since .global_var is obscure enough
for users, I think we might as well add a --param switch that controls
the heuristic used to trigger the creation of .global_var.
one of the things we have to do to integrate with the mainline anyway.
Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
---|---|---|
Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |