From: David Laight <David.Laight@ACULAB.COM>
To: buildroot@busybox.net
Subject: [Buildroot] [git commit branch/2021.02.x] Config.in: disable PIC/PIE for Nios2
Date: Thu, 10 Jun 2021 15:32:51 +0000 [thread overview]
Message-ID: <35e591b01b1b4b9d8d804b37d143d139@AcuMS.aculab.com> (raw)
In-Reply-To: <87mtrxkbdy.fsf@dell.be.48ers.dk>
From: Peter Korsgaard
> Sent: 10 June 2021 16:06
>
> >>>>> "David" == David Laight <David.Laight@ACULAB.COM> writes:
>
> Hi,
>
> >> Recently in Buildroot the option BR2_PIC_PIE has been enabled by default along
> >> with other hardening features [1]. Since then the nios2 defconfig
> >> qemu_nios2_10m50_defconfig is failing to boot due to a segfault in init program:
>
> > You probably just don't want to enable PIE for nios2 at all.
>
> Notice that this commit was about disallowing PIE for nios2.
Indeed, but maybe you want a stronger note that you really
don't want any of the 'hardening' features on such a slow processor.
...
> Yes, I also cannot recommend people using nios2 (or microblaze for that
> matter) for Linux systems.
Never mind Linux, I don't think I'd even run VxWorks.
We have about 4 instructions to set up %sp and then jump
straight to the C code loop.
No os, no libc, no nothing, just a code loop.
The one that does 64 channels of 64k hdlc (for SS7) running
at 62.5MHz doesn't ever write to the stack.
I did 'cheat', there are some custom instructions for the
bitstuffing and abort/flag detection.
David
-
Registered Address Lakeside, Bramley Road, Mount Farm, Milton Keynes, MK1 1PT, UK
Registration No: 1397386 (Wales)
prev parent reply other threads:[~2021-06-10 15:32 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-06-10 8:20 [Buildroot] [git commit branch/2021.02.x] Config.in: disable PIC/PIE for Nios2 Peter Korsgaard
2021-06-10 14:28 ` David Laight
2021-06-10 15:06 ` Peter Korsgaard
2021-06-10 15:32 ` David Laight [this message]
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=35e591b01b1b4b9d8d804b37d143d139@AcuMS.aculab.com \
--to=david.laight@aculab.com \
--cc=buildroot@busybox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.