This is the mail archive of the 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: Keeping unreachable code

On Sunday 03 February 2002 19:52, you wrote:
> >>You don't.   Put it in assembly outside the function where it belongs.
> or make it a separate public function

So GCC will not throw away a function that it cannot see is called from 
anywhere? It is only a few instructions that is in this routine so I would 
prefer to keep it in the function if possible. It could be as simple as:

movl $1, %eax

Basicly, what I'm trying to do is to implement support in GCC for a form of 
exception handling where the OS dispatches an exception to a runtime library 
which then searches the stack for registered exception handlers and when one 
is found, a filter routine is called (like the small routine above). The 
filter routine determines if the exception handler will handle the exception 
and reports this information back to the runtime library.

For example.

int test()
    __try {
	// Protected region
	// Exception handler
  return 1;
EXCEPTION_EXECUTE_HANDLER is the filter routine - a constant that tells the 
runtime library to call the start of the __except block in the event that an 
exception occured (eg. an Access Violation). In the example above, if an 
exception occur when inside the protected region, control is transferred to 
the start of the exception handler. The __except block is executed and 
then "return 1" is executed and the function return as it normally would. 

GCC should generate a jump at the end of the __try block (it should jump to 
just after the end of the __except block) because the __except block should 
not be executed if no exception occur. This would cause GCC to throw away the 
exception handler like it does with the filter routine now.

So here I cannot use a new function for the __except block since control 
should flow normally out of the function even if an exception occur.

Isn't there any way to mark a block of code permanent?

Casper Hornstrup

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