On 1/7/10 2:41 PM, Kevin O'Connor wrote: > On Thu, Jan 07, 2010 at 10:09:23AM +0100, Stefan Reinauer wrote: > >> On 1/7/10 5:23 AM, Kevin O'Connor wrote: >> >>> I don't think the above is a problem (the pointer foo resides on the >>> stack, but the string contents do not). The following is a problem: >>> >>> const char foo[]="foobar\n"; >>> >>> (both the pointer and the array contents are on the stack), and indeed >>> this does generate a warning from gcc. >>> >>> >> Not with my default 4.3.2 -Wall -Wextra >> > That's odd. I used: ..
Hm.. seems I was wrong. I verified and I get the same message. Why didn't the code in coreboot trigger one? Stefan -- coresystems GmbH • Brahmsstr. 16 • D-79104 Freiburg i. Br. Tel.: +49 761 7668825 • Fax: +49 761 7664613 Email: i...@coresystems.de • http://www.coresystems.de/ Registergericht: Amtsgericht Freiburg • HRB 7656 Geschäftsführer: Stefan Reinauer • Ust-IdNr.: DE245674866 -- coreboot mailing list: coreboot@coreboot.org http://www.coreboot.org/mailman/listinfo/coreboot