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: [3.3 regression?] flag_hosted and back-ends


> Date: Fri, 14 Mar 2003 16:22:36 -0800
> From: Jason R Thorpe <thorpej at wasabisystems dot com>

> On Fri, Mar 14, 2003 at 03:54:18PM -0800, Geoff Keating wrote:
> 
>  > Why can't GRUB supply its own __enable_execute_stack function, that
>  > does whatever the right thing is for GRUB's environment?
> 
> I can see a couple of reasons why that would not be appropriate:
> 
> 	* Random applications should not have to know about internal
> 	  routines in libgcc.

GRUB is not a 'random application'.  It's a very small operating
system.  Since this is an operating system interface, I don't think
it's unreasonable that GRUB should need to know about it.

> 	* An application that uses -ffreestanding has pretty much
> 	  told the compiler "don't assume I'm in a hosted environment".
> 	  The __enable_execute_stack() function *does* assume a hosted
> 	  environment.  It seems perfectly logical that it should not
> 	  be used if the application is free-standing.

I don't see how your logic distinguishes __enable_execute_stack from
memcpy.  I also don't see how __enable_execute_stack assumes a hosted
environment; for instance, surely GRUB hasn't disabled the icache?

-- 
- Geoffrey Keating <geoffk at geoffk dot org>


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