[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [MiNT] Stack problems with GCC 4

To: Alan Hourihane <alanh@fairlite.demon.co.uk>
Subject: Re: [MiNT] Stack problems with GCC 4
From: Andreas Schwab <schwab@suse.de>
Date: Mon, 24 Dec 2007 10:16:31 +0100
Cc: mint <mint@fishpool.com>
Delivered-to: fnaumann@mail.boerde.de
In-reply-to: <1198456590.9451.17.camel@localhost> (Alan Hourihane's message of "Mon\, 24 Dec 2007 00\:36\:30 +0000")
List-help: <mailto:ecartis@lists.fishpool.fi?Subject=help>
List-id: <mint.lists.fishpool.fi>
List-owner: <mailto:tjhukkan@fishpool.fi>
List-post: <mailto:mint@lists.fishpool.fi>
List-subscribe: <mailto:mint-request@lists.fishpool.fi?Subject=subscribe>
List-unsubscribe: <mailto:mint-request@lists.fishpool.fi?Subject=unsubscribe>
References: <1198456590.9451.17.camel@localhost>
Sender: mint-bounce@lists.fishpool.fi
User-agent: Gnus/5.110006 (No Gnus v0.6) Emacs/22.1 (gnu/linux)

Alan Hourihane <alanh@fairlite.demon.co.uk> writes:

> There's a compiler option in GCC 4 too called
> -fno-zero-initialized-in-bss which allows stksiz.c to be compiled
> without any patch and correctly puts _stksiz into the data section, but
> then GCC 2.x can't compile the code because it doesn't understand the
> flag.

What about __attribute__((section(".data")))?

Andreas.

-- 
Andreas Schwab, SuSE Labs, schwab@suse.de
SuSE Linux Products GmbH, Maxfeldstraße 5, 90409 Nürnberg, Germany
PGP key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."

Follow-Ups:
- Re: [MiNT] Stack problems with GCC 4
  - From: Alan Hourihane <alanh@fairlite.demon.co.uk>

References:
- [MiNT] Stack problems with GCC 4
  - From: Alan Hourihane <alanh@fairlite.demon.co.uk>

Prev by Date: Re: [MiNT] Stack problems with GCC 4
Next by Date: Re: [MiNT] Stack problems with GCC 4
Previous by thread: Re: [MiNT] Stack problems with GCC 4
Next by thread: Re: [MiNT] Stack problems with GCC 4
Index(es):
- Date
- Thread