From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from mail-wm1-x333.google.com (mail-wm1-x333.google.com [IPv6:2a00:1450:4864:20::333]) by sourceware.org (Postfix) with ESMTPS id 4A18E3858C83 for ; Sun, 27 Mar 2022 07:41:38 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 4A18E3858C83 Received: by mail-wm1-x333.google.com with SMTP id n35so6640015wms.5 for ; Sun, 27 Mar 2022 00:41:38 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=v/aHLr2XSB8qIZSp0iv8iNp3ObYveXm+ckNOjuPM5Fk=; b=ZdQF4SY2G7I5yJrJz7YcwGkMMRasJvw3yXIpR71W65U3U+iEaSjP90HIfho2bSP9ko DctD/NTVQlXMR/Fp7+nxcOVfQ4Air6YuKz5HtuYnW/ciUNYQyWHI4WDxBQBKWOj13IO1 S+Km2RWGuvlVNNPBg7oMT4v1wABnPZjdiZJxGKuQCMjkkgHfeZPYRVjJs9d2styuY7uV y4QjlL9UVIcT78LZ2lH3kBGy1qVCOWJeCPsSt91qeJz+xq5WpDarKnsIL3SsmdfPnX4N 3MXcPrUOjfcU0MOUiw3g6cfIxrjrBsq8HCY188txqXCQuPS3JORmmi2lfEmXpavXxgzq b+4A== X-Gm-Message-State: AOAM532/J/+SyUmlH8axf3m+I1t83WZkWlcpgYBx5AaZgzOSErzBA+SE kjnCIjO9FcrUKNSYqg7VtrvZ3vf2ywap25RTDaw= X-Google-Smtp-Source: ABdhPJxy+Bo6VNqaMMNqUcRxRXaIp5y6sZea2CKTVRHALUWIlw/37vPghPGIYTQDjhN0AICSbox3QewQMURvfHKeOcY= X-Received: by 2002:a7b:c017:0:b0:38c:8a13:466d with SMTP id c23-20020a7bc017000000b0038c8a13466dmr28180754wmb.128.1648366896845; Sun, 27 Mar 2022 00:41:36 -0700 (PDT) MIME-Version: 1.0 References: <11cb0554516ea651ca9d668d5748786ab675acef.camel@posteo.net> In-Reply-To: <11cb0554516ea651ca9d668d5748786ab675acef.camel@posteo.net> From: Jonathan Wakely Date: Sun, 27 Mar 2022 07:41:25 +0000 Message-ID: Subject: Re: Help with bisecting a test suite regression in GCC To: John Scott Cc: gcc-help Content-Type: text/plain; charset="UTF-8" X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00, DKIM_SIGNED, DKIM_VALID, DKIM_VALID_AU, DKIM_VALID_EF, FREEMAIL_FROM, RCVD_IN_DNSWL_NONE, SPF_HELO_NONE, SPF_PASS, TXREP, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on server2.sourceware.org X-BeenThere: gcc-help@gcc.gnu.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Gcc-help mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 27 Mar 2022 07:41:39 -0000 On Sat, 26 Mar 2022 at 22:42, John Scott via Gcc-help wrote: > > Hi, > > While working on upgrading the gcc-sh-elf Debian package from gcc 11 to > gcc 12, I think I've found a regression. I'm able to reproduce it with > an upstream bare-metal build. > > I've had a hard time figuring out how to bisect it. A naive run with > git bisect start > git bisect new . "." is not a tag or commit revision. I don't know what this does. > git bisect old releases/gcc-11.2.0 This tag is on the gcc-11 branch, which is not in the history of gcc-12. I think what you want is: git bisect start git bisect new master git bisect old `git merge-base releases/gcc-11.2.0 master` This will bisect between the point where the gcc-11 branch was created and the current head of master. > > fails with > The merge base 250f234988b6231669a720c52101d3686d645072 is new. > The property has changed between 250f234988b6231669a720c52101d3686d645072 and [7ca388565af176bd4efd4f8db1e5e9e11e98ef45]. > error: bisect run failed: 'git bisect--helper --bisect-state (null)' exited with error code -3 > > I'm not enough of a Git or GCC wizard to get further. Does anyone have > any advice so I can make an informative bug report?