From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 56680 invoked by alias); 11 Oct 2016 18:51:22 -0000 Mailing-List: contact gcc-patches-help@gcc.gnu.org; run by ezmlm Precedence: bulk List-Id: List-Archive: List-Post: List-Help: Sender: gcc-patches-owner@gcc.gnu.org Received: (qmail 56671 invoked by uid 89); 11 Oct 2016 18:51:21 -0000 Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-1.4 required=5.0 tests=AWL,BAYES_00,RCVD_IN_DNSWL_NONE,RCVD_IN_SORBS_SPAM autolearn=no version=3.3.2 spammy= X-HELO: mail-oi0-f47.google.com Received: from mail-oi0-f47.google.com (HELO mail-oi0-f47.google.com) (209.85.218.47) by sourceware.org (qpsmtpd/0.93/v0.84-503-g423c35a) with ESMTP; Tue, 11 Oct 2016 18:51:20 +0000 Received: by mail-oi0-f47.google.com with SMTP id y2so34929590oie.0 for ; Tue, 11 Oct 2016 11:51:20 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=eMN8w/Bn2LQkQbBn6CVlUahtaKtn+jT1kKyB3K0+Kyw=; b=Qw4aMhDVU43izJRcrgICbm68hDlHkpNS/Qm5O3vMLlkIjiUuCQ4Zu2imxSPVj/RjuL 5CCWo8cSFt24aMSbXV0b0qX9XNfpApRmb6JvHwNn4qp99qPx3JlFmm3BIXF+oI0t4BIN VT9Bl0Yq70klwXWMMmuGtX4qzAWPBF41nZPiSyIpkHCILYt1rpwZK8ku6Ds4y3TTqCUI unTt0Ud95C7JjQ64WuphgMq8fTCvWSj94/wnBcT9CJsiDA6pBlxzoWKOBvEIorg7zIB+ jQudjh25o2GEHwt81a5KTqhvvmGTMDslwWdplNWHUEc4vHQ1XpjJiR+PzEsNQEw9JuRI 55Iw== X-Gm-Message-State: AA6/9Rn8LLKZ9j5O7N6aeB975pKteVD9uGvyFDxeBZWyc9it1qrDZ1zZohl0CO6wMyne+rhoUi65oUM826qyqqyG X-Received: by 10.157.34.18 with SMTP id o18mr2593343ota.112.1476211879055; Tue, 11 Oct 2016 11:51:19 -0700 (PDT) MIME-Version: 1.0 Received: by 10.182.87.231 with HTTP; Tue, 11 Oct 2016 11:50:58 -0700 (PDT) In-Reply-To: <6C68EDB9-5933-4127-978E-807ABC7F31C7@bell.net> References: <305D4697-79B3-4B69-8741-98BFC00A5ECE@bell.net> <856A3FEF-7A0D-43D4-9CBF-23939E7861C4@bell.net> <6C68EDB9-5933-4127-978E-807ABC7F31C7@bell.net> From: Jason Merrill Date: Tue, 11 Oct 2016 18:51:00 -0000 Message-ID: Subject: Re: [PATCH] Implement new hook for max_align_t_align To: John David Anglin Cc: Bernd Edlinger , "gcc-patches@gcc.gnu.org" , Jeff Law Content-Type: text/plain; charset=UTF-8 X-IsSubscribed: yes X-SW-Source: 2016-10/txt/msg00767.txt.bz2 /* Alignment, in bits, a C conformant malloc implementation has to provide. The HP-UX malloc implementation provides a default alignment of 8 bytes. This can be increased with mallopt. The glibc implementation also provides 8-byte alignment. Note that this isn't enough for various POSIX types such as pthread_mutex_t. However, since we no longer need the 16-byte alignment for atomic operations, we ignore the nominal alignment specified for these types. The same is true for long double on 64-bit HP-UX. */ If PA malloc doesn't actually provide 16-byte alignment, this change seems problematic; it will mean any type that wants 16-byte alignment will silently get 8-byte alignment instead. Jason