public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Mark Wielaard <mjw@redhat.com>
To: Roland McGrath <roland@hack.frob.com>
Cc: Szabolcs Nagy <szabolcs.nagy@arm.com>,
	"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>,
	Josh Stone <jistone@redhat.com>
Subject: Re: [PATCH] elf.h SHF_EXCLUDE signed int 31 bit shift triggers undefined behaviour.
Date: Thu, 26 Mar 2015 08:29:00 -0000	[thread overview]
Message-ID: <1427358539.28141.1.camel@bordewijk.wildebeest.org> (raw)
In-Reply-To: <20150325212521.0ACA12C3B93@topped-with-meat.com>

On Wed, 2015-03-25 at 14:25 -0700, Roland McGrath wrote:
> Please participate in the other thread trying to figure out a testing
> strategy.  I think it's tractable.

To be honest I am not as optimistic and like my simple one character
patch better. But if others are as positive as you are then I certainly
don't mind a different solution. As long as the problem gets fixed.

Cheers,

Mark

  reply	other threads:[~2015-03-26  8:29 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-24 10:39 Mark Wielaard
2015-03-24 14:13 ` Szabolcs Nagy
2015-03-24 19:50   ` Mike Frysinger
2015-03-24 19:53     ` Florian Weimer
2015-03-24 21:41       ` Mike Frysinger
2015-03-24 21:15   ` Mark Wielaard
2015-03-25 21:25     ` Roland McGrath
2015-03-26  8:29       ` Mark Wielaard [this message]
2015-04-21  9:21     ` Mark Wielaard
2015-04-22  8:15       ` Florian Weimer
2015-04-22  8:25         ` Andreas Schwab
2015-04-22  8:33           ` Florian Weimer
2015-04-22  8:59             ` Alexander Cherepanov
2015-04-22  8:59             ` Mark Wielaard
2015-04-22  9:18         ` Florian Weimer
2015-04-28  8:22           ` Mark Wielaard
2015-04-28 12:01             ` Florian Weimer
2015-05-13 10:27 ` Ondřej Bílka
2015-05-13 10:46   ` Mark Wielaard
2015-05-13 10:56     ` Ondřej Bílka
2015-05-14  0:43       ` Carlos O'Donell

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=1427358539.28141.1.camel@bordewijk.wildebeest.org \
    --to=mjw@redhat.com \
    --cc=jistone@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=roland@hack.frob.com \
    --cc=szabolcs.nagy@arm.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).