public inbox for devel@edk2.groups.io
 help / color / mirror / Atom feed
From: Leif Lindholm <leif.lindholm@linaro.org>
To: Ard Biesheuvel <ard.biesheuvel@linaro.org>
Cc: Laszlo Ersek <lersek@redhat.com>,
	"edk2-devel@lists.01.org" <edk2-devel@lists.01.org>,
	"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [PATCH] BaseTools/tools_def: suppress GCC predefined macros in DTB compilation
Date: Thu, 26 Oct 2017 12:33:09 +0100	[thread overview]
Message-ID: <20171026113309.i4thy2ardt2f6fw5@bivouac.eciton.net> (raw)
In-Reply-To: <CAKv+Gu-G6xvSqYcbDaOj2VHyACo93yVi3AU5X3e_VzvLzdvXkg@mail.gmail.com>

On Thu, Oct 26, 2017 at 12:11:16PM +0100, Ard Biesheuvel wrote:
> On 26 October 2017 at 12:09, Laszlo Ersek <lersek@redhat.com> wrote:
> > On 10/26/17 12:12, Ard Biesheuvel wrote:
> >> The standard GCC preprocessor we use to preprocess device tree sources
> >> files has a whole bunch of macros predefined, among which
> >>
> >
> > The example you wanted to paste is missing.
> >
> 
> Yeah, the leading # made git-commit throw them away :-)

Haha :)

> #define __linux 1
> #define __linux__ 1
> #define __gnu_linux__ 1
> #define linux 1

How did you make it not throw them away?
(I can find a few suggestions online, neither sounds optimal.)

> >> This causes a property like 'linux,code' to be converted into '1,code'
> >> which is obviously wrong. So let's get rid of all the predefined macros
> >> by passing -undef to the preprocessor command line.
> >>
> >> Contributed-under: TianoCore Contribution Agreement 1.1
> >> Signed-off-by: Ard Biesheuvel <ard.biesheuvel@linaro.org>
> >> ---
> >>  BaseTools/Conf/tools_def.template | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/BaseTools/Conf/tools_def.template b/BaseTools/Conf/tools_def.template
> >> index df7c109438fd..98df0ffc9294 100755
> >> --- a/BaseTools/Conf/tools_def.template
> >> +++ b/BaseTools/Conf/tools_def.template
> >> @@ -4369,7 +4369,7 @@ DEFINE GCC_VFRPP_FLAGS             = -x c -E -P -DVFRCOMPILE --include $(DEST_DI
> >>  DEFINE GCC_ASLPP_FLAGS             = -x c -E -include AutoGen.h
> >>  DEFINE GCC_ASLCC_FLAGS             = -x c
> >>  DEFINE GCC_WINDRES_FLAGS           = -J rc -O coff
> >> -DEFINE GCC_DTCPP_FLAGS             = -E -x assembler-with-cpp -imacros $(DEST_DIR_DEBUG)/AutoGen.h -nostdinc
> >> +DEFINE GCC_DTCPP_FLAGS             = -E -x assembler-with-cpp -imacros $(DEST_DIR_DEBUG)/AutoGen.h -nostdinc -undef
> >>  DEFINE GCC_IA32_RC_FLAGS           = -I binary -O elf32-i386          -B i386    --rename-section .data=.hii
> >>  DEFINE GCC_X64_RC_FLAGS            = -I binary -O elf64-x86-64        -B i386    --rename-section .data=.hii
> >>  DEFINE GCC_IPF_RC_FLAGS            = -I binary -O elf64-ia64-little   -B ia64    --rename-section .data=.hii
> >>
> >
> > With the commit message fixed:
> >
> > Acked-by: Laszlo Ersek <lersek@redhat.com>

With the same precondition:

Reviewed-by: Leif Lindholm <leif.lindholm@linaro.org>

/
    Leif


  reply	other threads:[~2017-10-26 11:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-10-26 10:12 [PATCH] BaseTools/tools_def: suppress GCC predefined macros in DTB compilation Ard Biesheuvel
2017-10-26 11:09 ` Laszlo Ersek
2017-10-26 11:11   ` Ard Biesheuvel
2017-10-26 11:33     ` Leif Lindholm [this message]
2017-10-26 11:34       ` Ard Biesheuvel
2017-10-26 15:08         ` Laszlo Ersek
2017-10-31  5:41 ` Gao, Liming
2017-10-31  8:27   ` Ard Biesheuvel

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-list 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=20171026113309.i4thy2ardt2f6fw5@bivouac.eciton.net \
    --to=devel@edk2.groups.io \
    /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