public inbox for gcc-patches@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jeff Law <law@redhat.com>
To: Trevor Saunders <tbsaunde@tbsaunde.org>
Cc: Jan-Benedict Glaw <jbglaw@lug-owl.de>,
	       Trevor Saunders <tbsaunde+gcc@tbsaunde.org>,
	       "Moore, Catherine" <Catherine_Moore@mentor.com>,
	       Denis Chertykov <chertykov@gmail.com>,
	       Eric Christopher <echristo@gmail.com>,
	       Matthew Fortune <matthew.fortune@imgtec.com>,
	       David Edelsohn <dje.gcc@gmail.com>,
	       Alexandre Oliva <aoliva@redhat.com>,
	Kaz Kojima <kkojima@gcc.gnu.org>,
	       Oleg Endo <olegendo@gcc.gnu.org>,
	Jonathan Wakely <jwakely@redhat.com>,
	       gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: config-list.mk and obsoleted configurations
Date: Thu, 17 Dec 2015 21:02:00 -0000	[thread overview]
Message-ID: <567322CE.6070300@redhat.com> (raw)
In-Reply-To: <20151217203111.GA13192@tsaunders-iceball.corp.tor1.mozilla.com>


>
> hWell, it might be the only target that has warnings because of that,
> but from a quick look it seems like any target that uses avr-stdint.h or
> newlib-stdint.h could theoretically have null values for those macros.
> Without a bit of digging I'm not sure how much of that is real and how
> much is completely theoretical archs that would have any number of other
> problems.
The other targets don't trip over it for various reasons.  You have to 
dig into how the target stuff is setup in the avr port.  I outlined it a 
while back then went and had a beer to erase the memory of how that 
stuff got expanded.

jeff

  reply	other threads:[~2015-12-17 21:02 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-06 21:48 [BUILDROBOT] "error: null argument where non-null required" on multiple targets Jan-Benedict Glaw
2015-12-14 18:54 ` Moore, Catherine
2015-12-14 20:07   ` Jan-Benedict Glaw
2015-12-15 17:44     ` Jeff Law
2015-12-16 10:46       ` Jan-Benedict Glaw
2015-12-17 18:05         ` Jeff Law
2015-12-17 18:34           ` config-list.mk and obsoleted configurations (was: [BUILDROBOT] "error: null argument where non-null required" on multiple targets) Jan-Benedict Glaw
2015-12-17 18:39             ` config-list.mk and obsoleted configurations Jeff Law
2015-12-17 18:58               ` Jan-Benedict Glaw
2015-12-17 19:53                 ` Jeff Law
2015-12-17 20:33                   ` Trevor Saunders
2015-12-17 21:02                     ` Jeff Law [this message]
2015-12-21 14:20           ` [BUILDROBOT] "error: null argument where non-null required" on multiple targets Moore, Catherine

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=567322CE.6070300@redhat.com \
    --to=law@redhat.com \
    --cc=Catherine_Moore@mentor.com \
    --cc=aoliva@redhat.com \
    --cc=chertykov@gmail.com \
    --cc=dje.gcc@gmail.com \
    --cc=echristo@gmail.com \
    --cc=gcc-patches@gcc.gnu.org \
    --cc=jbglaw@lug-owl.de \
    --cc=jwakely@redhat.com \
    --cc=kkojima@gcc.gnu.org \
    --cc=matthew.fortune@imgtec.com \
    --cc=olegendo@gcc.gnu.org \
    --cc=tbsaunde+gcc@tbsaunde.org \
    --cc=tbsaunde@tbsaunde.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).