This is the mail archive of the crossgcc@sourceware.org mailing list for the crossgcc project.
See the CrossGCC FAQ for lots more information.
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |
| Other format: | [Raw text] | |
On Wed, Dec 06, 2006 at 04:53:58PM -0500, Nicolas Pitre wrote: > In fact, the kernel doesn't care much about EABI full compliance. The > only requirement on the kernel to be able to run EABI userspace is to > have the same structure member alignment and function argument layout as > the "true" EABI compliance so the kernel and user space understand each > other across syscall boundaries. And using -mabi=aapcs worked just fine > for that so far regardless of the gcc config. > > If that behavior was not to hold true then gcc should not accept the > conflicting -mabi argument. But that would be unfortunate if it > happened. I would expect that much to work, though I haven't tried it myself, at least as long as you aren't silly about it (e.g. putting enum types in structs). -- Daniel Jacobowitz CodeSourcery -- For unsubscribe information see http://sourceware.org/lists.html#faq
| Index Nav: | [Date Index] [Subject Index] [Author Index] [Thread Index] | |
|---|---|---|
| Message Nav: | [Date Prev] [Date Next] | [Thread Prev] [Thread Next] |