public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "romain.naour at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c/98784] [gcc 8.4/9.3/10] sparcv8 regression
Date: Thu, 21 Jan 2021 23:26:59 +0000	[thread overview]
Message-ID: <bug-98784-4-iWEoqIMWdu@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-98784-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=98784

--- Comment #2 from Romain Naour <romain.naour at gmail dot com> ---
Hello,

The kernel and userland are built with the same toolchain, but this is the
userpace program (such busybox) that crash.

Busybox is built with the following flags:

Toolchain wrapper executing:
   
'qemu_sparc_ss10_defconfig/host/bin/sparc-buildroot-linux-uclibc-gcc.br_real'
    '--sysroot'
    'qemu_sparc_ss10_defconfig/host/sparc-buildroot-linux-uclibc/sysroot'
    '-Wp,-MD,libbb/.vfork_daemon_rexec.o.d'
    '-std=gnu99'
    '-Iinclude'
    '-Ilibbb'
    '-include'
    'include/autoconf.h'
    '-D_GNU_SOURCE'
    '-DNDEBUG'
    '-D_LARGEFILE_SOURCE'
    '-D_LARGEFILE64_SOURCE'
    '-D_FILE_OFFSET_BITS=64'
    '-DBB_VER="1.33.0"'
    '-D_LARGEFILE_SOURCE'
    '-D_LARGEFILE64_SOURCE'
    '-D_FILE_OFFSET_BITS=64'
    '-Os'
    '-Wall'
    '-Wshadow'
    '-Wwrite-strings'
    '-Wundef'
    '-Wstrict-prototypes'
    '-Wunused'
    '-Wunused-parameter'
    '-Wunused-function'
    '-Wunused-value'
    '-Wmissing-prototypes'
    '-Wmissing-declarations'
    '-Wno-format-security'
    '-Wdeclaration-after-statement'
    '-Wold-style-definition'
    '-finline-limit=0'
    '-fno-builtin-strlen'
    '-fomit-frame-pointer'
    '-ffunction-sections'
    '-fdata-sections'
    '-fno-guess-branch-probability'
    '-funsigned-char'
    '-static-libgcc'
    '-falign-functions=1'
    '-falign-jumps=1'
    '-falign-labels=1'
    '-falign-loops=1'
    '-fno-unwind-tables'
    '-fno-asynchronous-unwind-tables'
    '-fno-builtin-printf'
    '-Os'
    '-DKBUILD_BASENAME="vfork_daemon_rexec"'
    '-DKBUILD_MODNAME="vfork_daemon_rexec"'
    '-c'
    '-o'
    'libbb/vfork_daemon_rexec.o'
    'libbb/vfork_daemon_rexec.c'

So -fPIE is not used here but there is a side effect when the patch is applied.

Note: This is an initial report, I don't have any clue about the real issue.

Best regards,
Romain

  parent reply	other threads:[~2021-01-21 23:26 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-21 22:13 [Bug c/98784] New: " romain.naour at gmail dot com
2021-01-21 23:01 ` [Bug c/98784] " ebotcazou at gcc dot gnu.org
2021-01-21 23:26 ` romain.naour at gmail dot com [this message]
2021-01-21 23:43 ` ebotcazou at gcc dot gnu.org
2021-01-22  7:33 ` [Bug target/98784] [8/9/10/11 Regression] " rguenth at gcc dot gnu.org
2021-01-23 11:43 ` romain.naour at gmail dot com
2021-01-23 17:33 ` ebotcazou at gcc dot gnu.org
2021-01-23 20:07 ` romain.naour at gmail dot com
2021-01-23 21:56 ` [Bug target/98784] [8/9/10/11 Regression] problematic build of uClibc with -fPIC ebotcazou at gcc dot gnu.org
2021-01-24  9:17 ` ebotcazou at gcc dot gnu.org
2021-01-26 21:24 ` romain.naour at gmail dot com
2021-01-26 22:29 ` romain.naour at gmail dot com
2021-04-09  8:08 ` rguenth at gcc dot gnu.org
2021-05-14  9:54 ` [Bug target/98784] [9/10/11/12 " jakub at gcc dot gnu.org
2021-06-01  8:19 ` rguenth at gcc dot gnu.org
2021-06-28 16:40 ` yann at sionneau dot net
2021-06-28 16:50 ` yann at sionneau dot net
2022-05-27  9:44 ` [Bug target/98784] [10/11/12/13 " rguenth at gcc dot gnu.org
2022-06-28 10:43 ` jakub at gcc dot gnu.org
2023-07-07 10:38 ` [Bug target/98784] [11/12/13/14 " rguenth at gcc dot gnu.org
2023-08-08  9:51 ` wbx at openadk dot org
2024-04-30 15:05 ` [Bug target/98784] [11/12/13/14/15 " dm.chestnykh at gmail dot com
2024-04-30 17:55 ` dm.chestnykh at gmail dot com
2024-04-30 17:59 ` pinskia at gcc dot gnu.org

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=bug-98784-4-iWEoqIMWdu@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=gcc-bugs@gcc.gnu.org \
    /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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).