Well, top-level assembly is usually nasty. Setting the section in the assembly statement as you said is probably the only thing you *can* do.
You'll probably need to (at the end of the asm block) restore the current section to what it was before (".previous"), too.
I don't think there is any requirement that top-level assembly statements get the section set to .text on their behalf.
Correct. Segher - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/
- Follow-Ups:
- Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- From: Willy Tarreau <w@1wt.eu>
- Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- References:
- Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- From: Axel Reinhold <axel@freakout.de>
- Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- From: Willy Tarreau <w@1wt.eu>
- Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- From: Segher Boessenkool <segher@kernel.crashing.org>
- Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- From: Willy Tarreau <w@1wt.eu>
- Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- From: "H. Peter Anvin" <hpa@zytor.com>
- Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- From: Willy Tarreau <w@1wt.eu>
- Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- From: "H. Peter Anvin" <hpa@zytor.com>
- Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- Prev by Date: Re: [PATCH] i386: convert mm_context_t semaphore to a mutex
- Next by Date: Re: 2.6.20->2.6.21 - networking dies after random time
- Previous by thread: Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- Next by thread: Re: Kernel Bug in 2.4.35 when compiled gcc>=4.2.0 and -march=c3
- Index(es):
![]() |