public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Steve Ellcey <sellcey@cavium.com>
To: Martin Sebor <msebor@gmail.com>, Joseph Myers <joseph@codesourcery.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
	Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: [PATCH] add attribute nonstring
Date: Wed, 15 Nov 2017 22:09:00 -0000	[thread overview]
Message-ID: <1510783744.1836.25.camel@cavium.com> (raw)
In-Reply-To: <11c4caec-df98-12e6-c6f5-cfc95eb8b8d6@gmail.com>

On Fri, 2017-11-10 at 16:11 -0700, Martin Sebor wrote:
> 
> Okay, thanks.  I've read that you run periodic Glibc builds with
> the latest GCC so I wanted to give you a heads up on this change
> and the patch to avoid breaking them.  Unless that's not a concern
> (do you use -Werror in those builds?) what is the best way to
> coordinate this update?
> 
> I CC Paul for his input in case updating tzcode first is important.
> 
> Martin

Martin, were you going to update this patch with Joseph's comments and
resubmit?  The tz changes are checked in and the ifreq struct is taken
care of so all that remains are the changes to cdefs.h to define
__NONSTRING and then to use in utmp.h.  I don't have any comments on
that change beyond what Joseph made but I did do a build and run on
aarch64 with the latest GCC to verify that those changes work for me.

Steve Ellcey
sellcey@cavium.com

  parent reply	other threads:[~2017-11-15 22:09 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-11-10 17:31 Martin Sebor
2017-11-10 17:54 ` Joseph Myers
2017-11-10 23:11   ` Martin Sebor
2017-11-10 23:46     ` Joseph Myers
2017-11-14 17:58       ` Joseph Myers
2017-11-15 22:09     ` Steve Ellcey [this message]
2017-11-15 23:05       ` Martin Sebor
2017-11-15 23:14         ` Joseph Myers
2017-11-21  5:27           ` Paul Eggert
2017-11-21 13:38             ` Joseph Myers
2017-11-12  9:06 ` Paul Eggert
2017-11-12 17:33   ` Martin Sebor
2017-11-12 20:39     ` Paul Eggert
2017-11-12 23:49       ` Martin Sebor
2017-11-13 17:35         ` Steve Ellcey
2017-11-14 16:37           ` Joseph Myers
2017-11-14 16:50           ` Florian Weimer
2017-11-14 17:06             ` Joseph Myers
2017-11-14 17:55               ` Andreas Schwab
2017-11-14 18:21                 ` Florian Weimer
2017-11-14 18:27                   ` Joseph Myers
2017-11-14 18:29                     ` Florian Weimer
2017-11-14 23:22                       ` Steve Ellcey
2017-11-15 10:48                         ` Florian Weimer
2017-11-15 17:58                           ` glibc failures on aarch64: (Was Re: [PATCH] add attribute nonstring) Steve Ellcey
2017-11-16  0:37                             ` Adhemerval Zanella
2017-11-17 12:49                             ` Szabolcs Nagy
2017-11-17 12:57                               ` Florian Weimer
2017-11-13  0:50   ` [PATCH] add attribute nonstring Joseph Myers
2017-11-27 11:05 ` Siddhesh Poyarekar
2017-11-27 16:04   ` Martin Sebor
2017-11-27 16:24     ` Siddhesh Poyarekar
2017-11-27 16:26       ` Siddhesh Poyarekar

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=1510783744.1836.25.camel@cavium.com \
    --to=sellcey@cavium.com \
    --cc=eggert@cs.ucla.edu \
    --cc=joseph@codesourcery.com \
    --cc=libc-alpha@sourceware.org \
    --cc=msebor@gmail.com \
    /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).