From: Denis Vlasenko <vda@port.imtp.ilyichevsk.odessa.ua>
To: Andi Kleen <ak@muc.de>
Subject: Re: [PATCH] Make gcc -align options .config-settable
Date: Fri, 8 Oct 2004 23:46:24 +0300
User-Agent: KMail/1.5.4
Cc: linux-kernel@vger.kernel.org
References: <2KBq9-2S1-15@gated-at.bofh.it> <200410081710.58766.vda@port.imtp.ilyichevsk.odessa.ua> <20041008154227.GA91816@muc.de>
In-Reply-To: <20041008154227.GA91816@muc.de>
MIME-Version: 1.0
Content-Type: text/plain;
  charset="koi8-r"
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
Message-Id: <200410082346.24150.vda@port.imtp.ilyichevsk.odessa.ua>
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1156
Lines: 32

> > > I would just do a single CONFIG_NO_ALIGNMENTS that sets everything to
> > > 1, that should be enough.
> > 
> > For me, yes, but there are people which are slightly less obsessed
> > with code size than me.
> > 
> > They might want to say "try to align to 16 bytes if
> > it costs less than 5 bytes" etc.
> 
> If they want to go down to that low level they can as well edit
> the Makefiles. But we already have far too many configs and
> adding new ones for obscure compiler options is not a good idea.
> 
> Also we don't normally add stuff "just in case", but only when
> people actually use it.

I have a suspicion that if I had submitted CONFIG_NO_ALIGNMENTS
patch instead, there would be comments from another crowd,
about it being too coarse.

Look at the post of Grzegorz Kulewski.

Anyway, I don't have strong preference. I just want to be at least
able to disable code alignment completely.
--
vda

-
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/