From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <gcc-bugzilla@gcc.gnu.org>
Received: by sourceware.org (Postfix, from userid 48)
 id 9A8163857C40; Wed, 12 Aug 2020 12:45:09 +0000 (GMT)
DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 9A8163857C40
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gcc.gnu.org;
 s=default; t=1597236309;
 bh=Xz6bU8I5KXiqLCh5b6kMT1z8QSStVfTl6KvqQqL0jHQ=;
 h=From:To:Subject:Date:From;
 b=Sx52fB19tACW9SeVAjXgRY2ZZgKWhTstODLvbGBHpCDpqc1elOcYfZiaJDw7I0Gjt
 kUSY3LurDoymwf5lQkXISV+WoIiTHLAMEv8Z2EyuyfErN2C19rbmgs+LuMuPxdOZUp
 DcWqptTwHK9+UtOxXlRAh0dq76BZSG57P9wnJy/c=
From: "vries at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/96588] New: [nvptx] Add -minit-limit
Date: Wed, 12 Aug 2020 12:45:09 +0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: new
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: target
X-Bugzilla-Version: 11.0
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: enhancement
X-Bugzilla-Who: vries at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution: 
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: bug_id short_desc product version bug_status
 bug_severity priority component assigned_to reporter target_milestone
Message-ID: <bug-96588-4@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-BeenThere: gcc-bugs@gcc.gnu.org
X-Mailman-Version: 2.1.29
Precedence: list
List-Id: Gcc-bugs mailing list <gcc-bugs.gcc.gnu.org>
List-Unsubscribe: <https://gcc.gnu.org/mailman/options/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=unsubscribe>
List-Archive: <https://gcc.gnu.org/pipermail/gcc-bugs/>
List-Post: <mailto:gcc-bugs@gcc.gnu.org>
List-Help: <mailto:gcc-bugs-request@gcc.gnu.org?subject=help>
List-Subscribe: <https://gcc.gnu.org/mailman/listinfo/gcc-bugs>,
 <mailto:gcc-bugs-request@gcc.gnu.org?subject=subscribe>
X-List-Received-Date: Wed, 12 Aug 2020 12:45:09 -0000

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=3D96588

            Bug ID: 96588
           Summary: [nvptx] Add -minit-limit
           Product: gcc
           Version: 11.0
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: P3
         Component: target
          Assignee: unassigned at gcc dot gnu.org
          Reporter: vries at gcc dot gnu.org
  Target Milestone: ---

[ As proposed in PR96566. ]

When compiling test-case gcc.dg/builtin-object-size-21.c for nvptx, we time
out, possibly while consuming a lot of disk space.

This has now been fixed for that testcase by requiring effective target
large_initializer, but for new test-cases that doesn't help.

We could add a nvptx option -minit-limit, set to unlimited by default, and =
then
add say -minit-limit=3D0xfffffff in nvptx-none-run.exp to make sure that we=
 run
into an error rather than a timeout/out-of-disk-space.=