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]

Re: [tree-ssa mudflap] source file/line locations


On Sat, Aug 31, 2002 at 05:54:10AM -0400, Frank Ch. Eigler wrote:
> What's the alternative?  At this point, a single location string
> is given to each __mf_check call.

There are lots of solutions, depending on how elaborate
you want to get.  Do you store this location, or only 
use it immedately if the check fails?

I think the most clever solution would be to use the debug
information present in the executable image, using the return
address of the __mf_check call as the location key.  This
would require no extra arguments and no extra runtime data.
In theory, you only have overhead when errors are encountered.

That's likely too complicated for the short-term.


r~


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