public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "chauhann at synopsys dot com" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug c++/99770] New: gcc gives warning being treated as error on arm platform
Date: Thu, 25 Mar 2021 12:16:01 +0000	[thread overview]
Message-ID: <bug-99770-4@http.gcc.gnu.org/bugzilla/> (raw)

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

            Bug ID: 99770
           Summary: gcc gives warning being treated as error on arm
                    platform
           Product: gcc
           Version: unknown
            Status: UNCONFIRMED
          Severity: normal
          Priority: P3
         Component: c++
          Assignee: unassigned at gcc dot gnu.org
          Reporter: chauhann at synopsys dot com
  Target Milestone: ---

I am trying to compile a file on aarch64 ARM platform but got error as follows:

SCompile.cxx: In constructor ‘SValidityCheck::SValidityCheck()’:
2361 SCompile.cxx:544:60: error: passing NULL to non-pointer argument 1 of
‘std::unordered_set<_Value, _Hash, _Pred, _Alloc>::unordered_set(std::unord    
ered_set<_Value, _Hash, _Pred, _Alloc>::size_type, const hasher&, const
key_equal&, const allocator_type&)

[-Werror=conversion-null] cc1plus: all warnings being treated as errors

However, this doesn't give any error or warning on linux64 and compiles just
fine.

Is this a bug in gcc on arm?

gcc version being used here on both platform (linux64 and aarch64) is 7.3.

             reply	other threads:[~2021-03-25 12:16 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-25 12:16 chauhann at synopsys dot com [this message]
2021-03-25 12:19 ` [Bug c++/99770] " redi at gcc dot gnu.org
2021-03-25 12:22 ` redi at gcc dot gnu.org
2022-01-20 17:20 ` rearnsha 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-99770-4@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).