Message ID | 4e545e3f3d600e62ed6522e0ed6ef609a6fe8354.1683024857.git.aburgess@redhat.com |
---|---|
State | Committed |
Headers |
Return-Path: <gdb-patches-bounces+patchwork=sourceware.org@sourceware.org> X-Original-To: patchwork@sourceware.org Delivered-To: patchwork@sourceware.org Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id B2A1E3858C50 for <patchwork@sourceware.org>; Tue, 2 May 2023 10:55:08 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org B2A1E3858C50 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1683024908; bh=CuN/1TTk6TQC5yn0vArpQ8BQIbMHoB1NoebzqyLxe0c=; h=To:Cc:Subject:Date:List-Id:List-Unsubscribe:List-Archive: List-Post:List-Help:List-Subscribe:From:Reply-To:From; b=ZaR7cwxJkfydYZsxk6lXL512ryWRkhtwyvzawirITHHsPQJOLidyLXl2CsRUWmITE QA6VyIEyTacfboNK6i6yhTmYRu9iwMcYIxHP64l6pI7BltI+kJ01darjpvIAhrtHAI U7gVfBYlMVQW6VpD0S50k3zf7+NMwJzyDbLRqFnI= X-Original-To: gdb-patches@sourceware.org Delivered-To: gdb-patches@sourceware.org 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 43E253858D1E for <gdb-patches@sourceware.org>; Tue, 2 May 2023 10:54:45 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.2 sourceware.org 43E253858D1E Received: from mail-wr1-f69.google.com (mail-wr1-f69.google.com [209.85.221.69]) by relay.mimecast.com with ESMTP with STARTTLS (version=TLSv1.3, cipher=TLS_AES_256_GCM_SHA384) id us-mta-79-bnlNIiZnOAWsYVMZlSC25A-1; Tue, 02 May 2023 06:54:43 -0400 X-MC-Unique: bnlNIiZnOAWsYVMZlSC25A-1 Received: by mail-wr1-f69.google.com with SMTP id ffacd0b85a97d-2ff4bc7a6a3so2198372f8f.3 for <gdb-patches@sourceware.org>; Tue, 02 May 2023 03:54:43 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1683024882; x=1685616882; h=content-transfer-encoding:mime-version:message-id:date:subject:cc :to:from:x-gm-message-state:from:to:cc:subject:date:message-id :reply-to; bh=CuN/1TTk6TQC5yn0vArpQ8BQIbMHoB1NoebzqyLxe0c=; b=SCUkc1nGB813193HdOZvgBfgt7Jvbjp5blyro7DPTstLTZRLaeeVjtVdowRB4JftFn VN3HEF173ckT2fmx4raXnL/RNaEdCweclzVqBJfRq/1NxvJbqXLoNK4fhPd5d1YoAk1u NAHyjS6OmpH/R0Mt+JzTnDVwuHz9/v1pRcLnQV+NA804+Jo6IRatlUkAHHYSeOjX1MUR M6+2UsyuIbFC6RV8d6QmLEUJ9KHjjUUyZ/PIxCmohp3cu5znEz9bBWNiA4NKaguj7SYj iAEqDWGsJTm+rgD4RACV5V7JfajcS7VFb1lOkH9Uj6aQTJYkWDupodc1zhMb7e0+Z8+Z Qoew== X-Gm-Message-State: AC+VfDwdzBVDWP7kXg6Dbst/gzOBL8KEvKusEgMiKXWsXRDqWNsHWk6y s55yloM5LW0FtqwF1dQ75TVbue2jrg4gi2iWc1XFNdHvDrF8etz7g/OliJVGV3VsZPg3rSsNWOB QAeSVrwMU1dIQJ7qy7GRYVMOlkf9d+frRTx2v1MpzSMGgY6fJw+60qQjhrWDwo+Lb6juwPjX3Tr K1Bexmqw== X-Received: by 2002:adf:db8e:0:b0:2fe:f2d1:dcab with SMTP id u14-20020adfdb8e000000b002fef2d1dcabmr12086248wri.58.1683024882356; Tue, 02 May 2023 03:54:42 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ4xZ1ZePYWmzl2j4e8+c0huGz+/uvLK8+ixAR3BkDmT5LhsJaHu5vMEt4/vJ548tnXNC/ThqQ== X-Received: by 2002:adf:db8e:0:b0:2fe:f2d1:dcab with SMTP id u14-20020adfdb8e000000b002fef2d1dcabmr12086234wri.58.1683024881960; Tue, 02 May 2023 03:54:41 -0700 (PDT) Received: from localhost (11.72.115.87.dyn.plus.net. [87.115.72.11]) by smtp.gmail.com with ESMTPSA id j5-20020a5d6045000000b0030626f69ee7sm7622726wrt.38.2023.05.02.03.54.41 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Tue, 02 May 2023 03:54:41 -0700 (PDT) To: gdb-patches@sourceware.org Cc: Andrew Burgess <aburgess@redhat.com> Subject: [PUSHED] gdb/testsuite: compile gdb.linespec/cp-completion-aliases.exp as C++ Date: Tue, 2 May 2023 11:54:39 +0100 Message-Id: <4e545e3f3d600e62ed6522e0ed6ef609a6fe8354.1683024857.git.aburgess@redhat.com> X-Mailer: git-send-email 2.25.4 MIME-Version: 1.0 X-Mimecast-Spam-Score: 0 X-Mimecast-Originator: redhat.com Content-Transfer-Encoding: 8bit Content-Type: text/plain; charset="US-ASCII"; x-default=true X-Spam-Status: No, score=-11.7 required=5.0 tests=BAYES_00, DKIMWL_WL_HIGH, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, GIT_PATCH_0, RCVD_IN_DNSWL_NONE, RCVD_IN_MSPIKE_H2, 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 X-BeenThere: gdb-patches@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gdb-patches mailing list <gdb-patches.sourceware.org> List-Unsubscribe: <https://sourceware.org/mailman/options/gdb-patches>, <mailto:gdb-patches-request@sourceware.org?subject=unsubscribe> List-Archive: <https://sourceware.org/pipermail/gdb-patches/> List-Post: <mailto:gdb-patches@sourceware.org> List-Help: <mailto:gdb-patches-request@sourceware.org?subject=help> List-Subscribe: <https://sourceware.org/mailman/listinfo/gdb-patches>, <mailto:gdb-patches-request@sourceware.org?subject=subscribe> From: Andrew Burgess via Gdb-patches <gdb-patches@sourceware.org> Reply-To: Andrew Burgess <aburgess@redhat.com> Errors-To: gdb-patches-bounces+patchwork=sourceware.org@sourceware.org Sender: "Gdb-patches" <gdb-patches-bounces+patchwork=sourceware.org@sourceware.org> |
Series |
[PUSHED] gdb/testsuite: compile gdb.linespec/cp-completion-aliases.exp as C++
|
|
Commit Message
Andrew Burgess
May 2, 2023, 10:54 a.m. UTC
Noticed in passing that the prepare_for_testing call in gdb.linespec/cp-completion-aliases.exp does not pass the 'c++' flag, despite this being a C++ test. I guess, as the source file has the '.cc' extension, all the compilers are doing the right thing anyway -- the source file uses templates, so is definitely being compiled as C++. I noticed this when I tried to set CXX_FOR_TARGET (but not CC_FOR_TARGET) and spotted that this script was still using the C compiler. Fixed in this commit by adding the 'c++' flag for prepare_for_testing. --- gdb/testsuite/gdb.linespec/cp-completion-aliases.exp | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) base-commit: b2499d8a40a6de13e9bc88b973a730bdf8b9b032
Comments
On 5/2/23 12:54, Andrew Burgess via Gdb-patches wrote: > Noticed in passing that the prepare_for_testing call in > gdb.linespec/cp-completion-aliases.exp does not pass the 'c++' flag, > despite this being a C++ test. > > I guess, as the source file has the '.cc' extension, all the compilers > are doing the right thing anyway -- the source file uses templates, so > is definitely being compiled as C++. > > I noticed this when I tried to set CXX_FOR_TARGET (but not > CC_FOR_TARGET) and spotted that this script was still using the C > compiler. > > Fixed in this commit by adding the 'c++' flag for prepare_for_testing. Hi, this is an instance of https://sourceware.org/bugzilla/show_bug.cgi?id=30380 . I already had this fixed in a branch, but hadn't had time to submit. FWIW, it's the top commit of https://github.com/vries/gdb/commits/testsuite/old-gcc . Thanks, - Tom > --- > gdb/testsuite/gdb.linespec/cp-completion-aliases.exp | 2 +- > 1 file changed, 1 insertion(+), 1 deletion(-) > > diff --git a/gdb/testsuite/gdb.linespec/cp-completion-aliases.exp b/gdb/testsuite/gdb.linespec/cp-completion-aliases.exp > index 33ad72e6f05..4c3ab7362e9 100644 > --- a/gdb/testsuite/gdb.linespec/cp-completion-aliases.exp > +++ b/gdb/testsuite/gdb.linespec/cp-completion-aliases.exp > @@ -20,7 +20,7 @@ load_lib completion-support.exp > > standard_testfile .cc > > -if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug}]} { > +if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug c++}]} { > return -1 > } > > > base-commit: b2499d8a40a6de13e9bc88b973a730bdf8b9b032
Tom de Vries <tdevries@suse.de> writes: > On 5/2/23 12:54, Andrew Burgess via Gdb-patches wrote: >> Noticed in passing that the prepare_for_testing call in >> gdb.linespec/cp-completion-aliases.exp does not pass the 'c++' flag, >> despite this being a C++ test. >> >> I guess, as the source file has the '.cc' extension, all the compilers >> are doing the right thing anyway -- the source file uses templates, so >> is definitely being compiled as C++. >> >> I noticed this when I tried to set CXX_FOR_TARGET (but not >> CC_FOR_TARGET) and spotted that this script was still using the C >> compiler. >> >> Fixed in this commit by adding the 'c++' flag for prepare_for_testing. > > Hi, > > this is an instance of > https://sourceware.org/bugzilla/show_bug.cgi?id=30380 . > > I already had this fixed in a branch, but hadn't had time to submit. > > FWIW, it's the top commit of > https://github.com/vries/gdb/commits/testsuite/old-gcc . Sorry for duplicating this work. I ran into this case while working on some other patch and I didn't want to have to carry around such a trivial local patch. Hope this didn't cause you any serious problems. Thanks, Andrew
diff --git a/gdb/testsuite/gdb.linespec/cp-completion-aliases.exp b/gdb/testsuite/gdb.linespec/cp-completion-aliases.exp index 33ad72e6f05..4c3ab7362e9 100644 --- a/gdb/testsuite/gdb.linespec/cp-completion-aliases.exp +++ b/gdb/testsuite/gdb.linespec/cp-completion-aliases.exp @@ -20,7 +20,7 @@ load_lib completion-support.exp standard_testfile .cc -if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug}]} { +if {[prepare_for_testing "failed to prepare" $testfile $srcfile {debug c++}]} { return -1 }