public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: Florian Weimer <fweimer@redhat.com>
Cc: GNU C Library <libc-alpha@sourceware.org>,
	"Carlos O'Donell" <carlos@redhat.com>,
	Mike Frysinger <vapier@gentoo.org>, Helge Deller <deller@gmx.de>
Subject: Re: [PATCH] hppa: Use generic pthread conditional variable support
Date: Sun, 12 Mar 2017 18:41:00 -0000	[thread overview]
Message-ID: <9A5DEAB6-7430-4260-9D73-A29C5011B80C@bell.net> (raw)
In-Reply-To: <37d468c7-221f-5aa6-f2e5-e70153b04f2b@redhat.com>

On 2017-03-12, at 1:59 PM, Florian Weimer wrote:

> On 03/12/2017 03:58 PM, John David Anglin wrote:
>> -    int __lock __attribute__ ((__aligned__(16)));
> 
> If this reduces the type alignment from 16 to 4, that's not acceptable because it changes application struct offsets when a condition variable is embedded into a struct.


I don't think so:

+    } __attribute__ ((__aligned__(16)));

Dave
--
John David Anglin	dave.anglin@bell.net



  reply	other threads:[~2017-03-12 18:41 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-12 14:58 John David Anglin
2017-03-12 17:59 ` Florian Weimer
2017-03-12 18:41   ` John David Anglin [this message]
2017-03-12 19:42 ` Torvald Riegel
2017-03-12 20:00   ` John David Anglin
2017-03-12 20:07     ` John David Anglin
2017-03-15  7:22     ` Mike Frysinger
2017-03-31 21:21 ` Aaro Koskinen
2017-03-31 22:35   ` John David Anglin
2017-04-01 14:01 ` [PATCH v2] hppa: Use generic pthread conditional variable support (BZ #21016) John David Anglin
2017-04-10 23:11   ` [PATCH v3] " John David Anglin
2017-06-04 16:51     ` [PATCH v4] " John David Anglin

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=9A5DEAB6-7430-4260-9D73-A29C5011B80C@bell.net \
    --to=dave.anglin@bell.net \
    --cc=carlos@redhat.com \
    --cc=deller@gmx.de \
    --cc=fweimer@redhat.com \
    --cc=libc-alpha@sourceware.org \
    --cc=vapier@gentoo.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 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).