From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <jwakely.gcc@gmail.com>
Received: from mail-ed1-x530.google.com (mail-ed1-x530.google.com
 [IPv6:2a00:1450:4864:20::530])
 by sourceware.org (Postfix) with ESMTPS id 105A6384B07D
 for <gcc@gcc.gnu.org>; Tue,  2 Aug 2022 06:35:56 +0000 (GMT)
DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 105A6384B07D
Received: by mail-ed1-x530.google.com with SMTP id r4so8649901edi.8
 for <gcc@gcc.gnu.org>; Mon, 01 Aug 2022 23:35:56 -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=5WwFEvkkYl8foAXHTWVj6iIldqWjqxRfve9YIBsrodg=;
 b=rInEDM5aEqn7GNfufIrQP2i2Bw31bKUh8gwCWXgvcwu+E+zXHP0qUHedF4vIfTBm8d
 y9ZzxKNJcMH8qBwqbUziVMayJ79G2bI/XwW/y+aUsfsSmvu5eFzLgas+1n751OIX9LK2
 3xoOVEXYEFWknsy+qKN0BmwOm5iJCjBSQzKUHvsV9+02wEqF4+F5qcxGgNeaLnYhy3z4
 V67gf01PVOXK4FZqrnDUAhFX4TSu0o9+4quan/3UgTzGneywM676x8j7QBTOXdxaI8vL
 I5AlNz/SEUcIUY83WfEmKKsNIIR3bRsrS+77hQ0rL6p5rihxNmpKjT6HN64qlASlN+WZ
 xi1w==
X-Gm-Message-State: AJIora/ixtIfvAVCoRRHy4IBm2X4UsLEsvnqFB1g3ERxXPZ8kz8q968D
 AE2C6RuQPlAZ7jsMQJ8vDGCPeyAYLqIe3/muYwI=
X-Google-Smtp-Source: AGRyM1v5OWFjE1Cb6+UwzK7S7I7GTy39NrURKo8z1QDDTEMPU+oQu+/Z3hatk7vpIW62i9uD7yQnrOwOAjzy3il8VVA=
X-Received: by 2002:a05:6402:3591:b0:43b:e8c8:a716 with SMTP id
 y17-20020a056402359100b0043be8c8a716mr19024592edc.356.1659422154854; Mon, 01
 Aug 2022 23:35:54 -0700 (PDT)
MIME-Version: 1.0
References: <CALDyosYzvPz=R1Dbn1hi8bskgfNbc1aRN5WJptYmHcm9yJ2Hog@mail.gmail.com>
 <CALDyosZzYJ9MTxroe9mfH+3cgmnnUUajQm6Dw+1+1W6-q6QVRA@mail.gmail.com>
In-Reply-To: <CALDyosZzYJ9MTxroe9mfH+3cgmnnUUajQm6Dw+1+1W6-q6QVRA@mail.gmail.com>
From: Jonathan Wakely <jwakely.gcc@gmail.com>
Date: Tue, 2 Aug 2022 07:35:43 +0100
Message-ID: <CAH6eHdRos6mAoCvOz9T7RcM61z7ywXcx0NHQWEQoiUWB3y8rLw@mail.gmail.com>
Subject: Re: Possible wrong-code bug in GCC?
To: Haoxin Tu <haoxintu@gmail.com>
Cc: GCC Mailing List <gcc@gcc.gnu.org>
Content-Type: text/plain; charset="UTF-8"
X-Spam-Status: No, score=-0.5 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 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: gcc@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc mailing list <gcc.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc>,
 <mailto:gcc-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc/>
List-Post: <mailto:gcc@gcc.gnu.org>
List-Help: <mailto:gcc-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc>,
 <mailto:gcc-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Tue, 02 Aug 2022 06:35:58 -0000

On Tue, 2 Aug 2022 at 05:45, Haoxin Tu via Gcc <gcc@gcc.gnu.org> wrote:
>
> Oh, sorry for the noise, there is an integer overflow that may cause
> undefined behavior.

You should check with UBsan before reporting something as a bug:

s.c:5:2: runtime error: signed integer overflow: 2147483647 + 1 cannot
be represented in type 'int'