This is the mail archive of the gcc@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]

Re: Optimization of conditional access to globals: thread-unsafe?

From: Robert Dewar <dewar at adacore dot com>
To: David Miller <davem at davemloft dot net>
Cc: dave dot korn at artimi dot com, matz at suse dot de, gcc at gcc dot gnu dot org
Date: Mon, 29 Oct 2007 07:24:40 -0400
Subject: Re: Optimization of conditional access to globals: thread-unsafe?
References: <Pine.LNX.4.64.0710281753210.23011@wotan.suse.de> <20071028.180108.71876074.davem@davemloft.net> <02e701c819c7$be985620$2e08a8c0@CAM.ARTIMI.COM> <20071028.183401.197068473.davem@davemloft.net>

One thing that seems missing from this thread is any quantitative
analysis of the value of this optimization. Although justifiable
from a formal point of view, whenever an optimization causes
difficulties for a significant number of users, it is important
to justify the optimization with clear data that it is really
valuable, otherwise it should be off by default.

Follow-Ups:
- Re: Optimization of conditional access to globals: thread-unsafe?
  - From: Michael Matz

References:
- Re: Optimization of conditional access to globals: thread-unsafe?
  - From: Michael Matz
- Re: Optimization of conditional access to globals: thread-unsafe?
  - From: David Miller
- RE: Optimization of conditional access to globals: thread-unsafe?
  - From: Dave Korn
- Re: Optimization of conditional access to globals: thread-unsafe?
  - From: David Miller

Index Nav:	[Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav:	[Date Prev] [Date Next]	[Thread Prev] [Thread Next]