public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "cvs-commit at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug target/97436] [nvptx] Remove -m32 support Date: Thu, 15 Oct 2020 13:26:32 +0000 [thread overview] Message-ID: <bug-97436-4-QswdGkBsA7@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-97436-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=97436 --- Comment #2 from CVS Commits <cvs-commit at gcc dot gnu.org> --- The master branch has been updated by Tom de Vries <vries@gcc.gnu.org>: https://gcc.gnu.org/g:34af17c0164f3138df094b144c7f74c2d1805444 commit r11-3953-g34af17c0164f3138df094b144c7f74c2d1805444 Author: Tom de Vries <tdevries@suse.de> Date: Thu Oct 15 11:37:43 2020 +0200 [nvptx] Remove -m32 The nvptx port has an -m32 option, but it's not clear whether this was ever build/tested/used. Don't expose to user anymore. Tested on nvptx. gcc/ChangeLog: 2020-10-15 Tom de Vries <tdevries@suse.de> PR target/97436 * config/nvptx/nvptx.opt (m32): Comment out. * doc/invoke.texi (NVPTX options): Remove -m32. gcc/testsuite/ChangeLog: 2020-10-15 Tom de Vries <tdevries@suse.de> PR target/97436 * gcc.target/nvptx/atomic_fetch-3.c: Remove.
next prev parent reply other threads:[~2020-10-15 13:26 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2020-10-15 7:57 [Bug target/97436] New: [nvptx] " vries at gcc dot gnu.org 2020-10-15 9:08 ` [Bug target/97436] " tschwinge at gcc dot gnu.org 2020-10-15 13:26 ` cvs-commit at gcc dot gnu.org [this message] 2020-10-15 13:34 ` [Bug target/97436] [nvptx] Remove " vries at gcc dot gnu.org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=bug-97436-4-QswdGkBsA7@http.gcc.gnu.org/bugzilla/ \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).