Linux M68K Architecture development
 help / color / mirror / Atom feed
From: John Paul Adrian Glaubitz <glaubitz@physik.fu-berlin.de>
To: Roger Shimizu <rogershimizu@gmail.com>, 877735@bugs.debian.org
Cc: Debian m68k <debian-68k@lists.debian.org>,
	Linux/m68k <linux-m68k@vger.kernel.org>
Subject: Re: Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS
Date: Thu, 5 Oct 2017 18:12:46 +0200	[thread overview]
Message-ID: <fb548f7a-eb98-949b-296c-fd031d8afa5f@physik.fu-berlin.de> (raw)
In-Reply-To: <CAEQ9gEmFPeibJUANPFbkTJfjyv6hLOG7Wr=ijyfrVSfRkKPEtw@mail.gmail.com>

On 10/05/2017 05:55 PM, Roger Shimizu wrote:
>> On second thought, I would actually recommended to revert this change
>> for all architectures. Size isn't so much a constraint anymore these
>> days, you reduce the binary by about 200k. I don't think this is worth
>> the risk of breaking something as fundemantal as busybox.
> 
> Please exclude armel, which has size limitation on initrd of d-i [0].
Hmm, ok. Is that currently actually a concern? If I'm seeing that correctly,
the "-Os" here only saved us around 200k. Does that already make a difference
on armel?

If yes, I'm also fine with something like

# On m68k, building with -Os leads to miscompiled code
ifeq (m68k,$(DEB_HOST_ARCH))
	CFLAGS := $(filter-out -Werror=format-security, ${CFLAGS})
else
	CFLAGS := $(filter-out -Werror=format-security -O2, ${CFLAGS})
endif

Adrian

-- 
  .''`.  John Paul Adrian Glaubitz
: :' :  Debian Developer - glaubitz@debian.org
`. `'   Freie Universitaet Berlin - glaubitz@physik.fu-berlin.de
   `-    GPG: 62FF 8A75 84E0 2956 9546  0006 7426 3B37 F5B5 F913

  reply	other threads:[~2017-10-05 16:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <150715899716.21351.14956363415364529265.reportbug@stretch64.physik.fu-berlin.de>
2017-10-05  7:25 ` Bug#877735: busybox: m68k build broken due to "-Os" in CFLAGS John Paul Adrian Glaubitz
2017-10-05 15:55   ` Roger Shimizu
2017-10-05 16:12     ` John Paul Adrian Glaubitz [this message]
2017-10-05 16:40       ` Steve McIntyre
2017-10-05 21:49         ` Christoph Biedl
2017-10-05 23:09           ` John Paul Adrian Glaubitz
2017-10-05 16:38   ` Steve McIntyre
2017-10-05 19:52     ` John Paul Adrian Glaubitz

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=fb548f7a-eb98-949b-296c-fd031d8afa5f@physik.fu-berlin.de \
    --to=glaubitz@physik.fu-berlin.de \
    --cc=877735@bugs.debian.org \
    --cc=debian-68k@lists.debian.org \
    --cc=linux-m68k@vger.kernel.org \
    --cc=rogershimizu@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox