All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Dannenberg <dannenberg@ti.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] [RFC] bug.h: Drop filename from BUG/WARNING logs if building for TPL/SPL
Date: Thu, 11 Jul 2019 13:50:13 -0500	[thread overview]
Message-ID: <20190711185013.qrynmdt3iejkbzhh@jiji> (raw)
In-Reply-To: <20190711184317.GG6891@bill-the-cat>

Hi Tom,

On Thu, Jul 11, 2019 at 02:43:17PM -0400, Tom Rini wrote:
> On Thu, Jul 11, 2019 at 01:12:16PM -0500, Andreas Dannenberg wrote:

<snip>

> > Also some additional background why I am even looking into this. One of
> > our platforms (AM335x) has a regression building on Travis CI with some
> > of our pending patches applied. Interestingly, this only happens on
> > Travis, which still uses GCC 7.3.0 for arm (why?). With newer, more
> > efficient compilers there is no such issue.
> 
> On this last point, gcc 7.3 is the current GCC release that doesn't have
> regressions elsewhere until we reach gcc-9, for which I cannot find good
> pre-built toolchains.  We can get gcc-8.3 (or 8.2?  I forget) from Arm
> Ltd now, but that has problems on x86.

Thanks for the background Tom, I wondered about the reasons behind.

Regards, Andreas


--
Andreas Dannenberg
Texas Instruments Inc

  reply	other threads:[~2019-07-11 18:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-07-10 21:30 [U-Boot] [RFC] bug.h: Drop filename from BUG/WARNING logs if building for TPL/SPL Andreas Dannenberg
2019-07-11 15:33 ` Andreas Dannenberg
2019-07-11 17:29   ` Masahiro Yamada
2019-07-11 18:12     ` Andreas Dannenberg
2019-07-11 18:43       ` Tom Rini
2019-07-11 18:50         ` Andreas Dannenberg [this message]
2019-07-12  7:11       ` Masahiro Yamada
2019-07-17 17:22 ` Tom Rini

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=20190711185013.qrynmdt3iejkbzhh@jiji \
    --to=dannenberg@ti.com \
    --cc=u-boot@lists.denx.de \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.