From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from us-smtp-delivery-124.mimecast.com (us-smtp-delivery-124.mimecast.com [170.10.129.124]) by sourceware.org (Postfix) with ESMTPS id CD0103858C36 for ; Wed, 6 Mar 2024 14:12:09 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org CD0103858C36 Authentication-Results: sourceware.org; dmarc=pass (p=none dis=none) header.from=redhat.com Authentication-Results: sourceware.org; spf=pass smtp.mailfrom=redhat.com ARC-Filter: OpenARC Filter v1.0.0 sourceware.org CD0103858C36 Authentication-Results: server2.sourceware.org; arc=none smtp.remote-ip=170.10.129.124 ARC-Seal: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1709734331; cv=none; b=ZpDZud/fpThamNFzKcnWWve+Jthv37/IaJCrfgQKILa+emZMBbxk5Q8H8QJxMjpS3rdtAOLQ0+cd7z6PTJcf7TWLXL8NyaIv+rfWAKHYxiiWA6h1oIkbBXqIL9EbPNz1MFe1tlUWO+YU4eQ0QdIVJq2aRixA/gU21VXz5Cz3JXE= ARC-Message-Signature: i=1; a=rsa-sha256; d=sourceware.org; s=key; t=1709734331; c=relaxed/simple; bh=miXFZQNzJrsOlSQCLRRwJ8RAZnsvZ7V2VznwsXMw3AI=; h=DKIM-Signature:Date:From:To:Subject:Message-ID:MIME-Version; b=s2z6v00tLi27cV8x9Zxxg9o+osW6VSjbZq4kZgGyCppUO187bp7W/LTL0h1taHP92zBzsUzKqVT5pvA4RkJfYA+YHA8ExX7wJM9qChxCtP2jJZB9q9UtnOpE3nhSAIxiyEwjrbCC0FxeZM9y6ryFRAklbiSnqgqziJ2FYBz/UPg= ARC-Authentication-Results: i=1; server2.sourceware.org DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=redhat.com; s=mimecast20190719; t=1709734329; h=from:from:reply-to:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:cc:mime-version:mime-version: content-type:content-type; bh=sHUENZGO0qphc0ktZiic4gXiM8R/GV4gggSkYNXv8i4=; b=O5k5Gs27PN6ZJe6kyr3T9BXGcwZwq05b/0R/4GVDbhuwAwnVpIXEt5+4PVCmfie7hLpSEc hc46/z/IajIAj3Vpz4Euti9tD9bCF3sAA3OWlEHuimplG+xmIsJNsPGKbAKgJ1aKBeuTfg ANSbzZA1WiV8Bu48F39e/jiM9Q9F3o0= Received: from mimecast-mx02.redhat.com (mimecast-mx02.redhat.com [66.187.233.88]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-459-kIcE4lsgPaqsg190DjG7tw-1; Wed, 06 Mar 2024 09:12:07 -0500 X-MC-Unique: kIcE4lsgPaqsg190DjG7tw-1 Received: from smtp.corp.redhat.com (int-mx02.intmail.prod.int.rdu2.redhat.com [10.11.54.2]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by mimecast-mx02.redhat.com (Postfix) with ESMTPS id 861A2101CC63 for ; Wed, 6 Mar 2024 14:12:07 +0000 (UTC) Received: from tucnak.zalov.cz (unknown [10.45.226.25]) by smtp.corp.redhat.com (Postfix) with ESMTPS id 4BF4140C6CB8; Wed, 6 Mar 2024 14:12:07 +0000 (UTC) Received: from tucnak.zalov.cz (localhost [127.0.0.1]) by tucnak.zalov.cz (8.17.1/8.17.1) with ESMTPS id 426EC50u4112085 (version=TLSv1.3 cipher=TLS_AES_256_GCM_SHA384 bits=256 verify=NOT); Wed, 6 Mar 2024 15:12:05 +0100 Received: (from jakub@localhost) by tucnak.zalov.cz (8.17.1/8.17.1/Submit) id 426EC5mr4112084; Wed, 6 Mar 2024 15:12:05 +0100 Date: Wed, 6 Mar 2024 15:12:05 +0100 From: Jakub Jelinek To: Jason Merrill Cc: gcc-patches@gcc.gnu.org Subject: C++ patch ping Message-ID: Reply-To: Jakub Jelinek MIME-Version: 1.0 X-Scanned-By: MIMEDefang 3.4.1 on 10.11.54.2 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Type: text/plain; charset=us-ascii Content-Disposition: inline X-Spam-Status: No, score=-3.6 required=5.0 tests=BAYES_00,DKIMWL_WL_HIGH,DKIM_SIGNED,DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,KAM_SHORT,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE,TXREP,T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on server2.sourceware.org List-Id: Hi! https://gcc.gnu.org/pipermail/gcc-patches/2024-February/thread.html#645781 [PATCH] c++: Fix up parameter pack diagnostics on xobj vs. varargs functions [PR113802] The thread contains two possible further versions of the patch. https://gcc.gnu.org/pipermail/gcc-patches/2024-February/thread.html#645782 [PATCH] dwarf2out: Emit DW_AT_export_symbols on anon unions/structs [PR113918] The thread contains another version of the patch at the end. https://gcc.gnu.org/pipermail/gcc-patches/2024-February/thread.html#645916 [PATCH] c-family, c++: Fix up handling of types which may have padding in __atomic_{compare_}exchange Seems Richi would like to use MEM_REF in the c-family code, that is then the https://gcc.gnu.org/pipermail/gcc-patches/2024-February/646040.html version. Thanks Jakub