public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "aaro.koskinen at iki dot fi" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/63691] GCC 4.9.x fails to build GLIBC 2.20 on HPPA
Date: Tue, 04 Nov 2014 19:36:00 -0000	[thread overview]
Message-ID: <bug-63691-4-0vhzxhs7VJ@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-63691-4@http.gcc.gnu.org/bugzilla/>

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

--- Comment #13 from Aaro Koskinen <aaro.koskinen at iki dot fi> ---
Created attachment 33884
  --> https://gcc.gnu.org/bugzilla/attachment.cgi?id=33884&action=edit
Preprocessed dl-conflict

Here's the preprocessed dl-conflict.c. In elf_machine_rela(), the sym_map gets
always assigned to 0, and in the following switch cases it's dereferenced
without any checks. Those are where the compiler will add abort refs.

When compiled with -fno-delete-null-pointer-checks GCC won't do that, but it's
not really related to any null pointer checks, instead the switch has also
other meanings, i.e. it's also telling the compiler that NULL deref is not
erroneous so it cannot make program fail on those. Or at least that's how I
understand it.


  parent reply	other threads:[~2014-11-04 19:36 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-30 21:19 [Bug target/63691] New: " aaro.koskinen at iki dot fi
2014-10-30 21:27 ` [Bug target/63691] " aaro.koskinen at iki dot fi
2014-10-31  0:29 ` dave.anglin at bell dot net
2014-10-31  0:49 ` pinskia at gcc dot gnu.org
2014-10-31  1:18 ` pinskia at gcc dot gnu.org
2014-10-31 18:43 ` aaro.koskinen at iki dot fi
2014-10-31 19:43 ` dave.anglin at bell dot net
2014-10-31 21:52 ` aaro.koskinen at iki dot fi
2014-11-01  8:17 ` schwab@linux-m68k.org
2014-11-01 11:32 ` aaro.koskinen at iki dot fi
2014-11-01 14:34 ` danglin at gcc dot gnu.org
2014-11-04 19:36 ` aaro.koskinen at iki dot fi [this message]
2021-11-28 14:43 ` danglin 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-63691-4-0vhzxhs7VJ@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).