All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andreas Schwab <schwab@linux-m68k.org>
To: Geert Uytterhoeven <geert@linux-m68k.org>
Cc: Randy Dunlap <rdunlap@infradead.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linux-m68k <linux-m68k@lists.linux-m68k.org>
Subject: Re: m68k allmodconfig build errors
Date: Wed, 26 Sep 2018 18:09:59 +0200	[thread overview]
Message-ID: <87a7o4dyug.fsf@igel.home> (raw)
In-Reply-To: <CAMuHMdW-ZA3bUJP3Fztm5sm7TSO345Jah471oMUr89x89d51xQ@mail.gmail.com> (Geert Uytterhoeven's message of "Wed, 26 Sep 2018 09:44:13 +0200")

On Sep 26 2018, Geert Uytterhoeven <geert@linux-m68k.org> wrote:

> Isn't gcc-8 just assuming that any char array must contain a valid
> NUL-terminated string, unless it is tagged with the nonstring attribute?

No, only if you call strncpy on it and make it potentially
non-terminated.

Andreas.

-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 7578 EB47 D4E5 4D69 2510  2552 DF73 E780 A9DA AEC1
"And now for something completely different."

      reply	other threads:[~2018-09-26 16:10 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-07-19 22:39 m68k allmodconfig build errors Randy Dunlap
2018-07-20  5:17 ` Finn Thain
2018-07-24  1:49   ` Randy Dunlap
2018-07-20  7:20 ` Andreas Schwab
2018-07-24  1:52   ` Randy Dunlap
2018-07-24  4:49     ` Finn Thain
2018-07-26 19:29       ` Randy Dunlap
2018-07-27  4:44         ` Finn Thain
2018-07-27  8:40           ` Andreas Schwab
2018-07-27 12:51             ` Finn Thain
2018-07-24 17:35     ` Andreas Schwab
2018-09-26  7:44       ` Geert Uytterhoeven
2018-09-26 16:09         ` Andreas Schwab [this message]

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=87a7o4dyug.fsf@igel.home \
    --to=schwab@linux-m68k.org \
    --cc=geert@linux-m68k.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-m68k@lists.linux-m68k.org \
    --cc=rdunlap@infradead.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 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.