From: Jeff Law <jlaw@ventanamicro.com>
To: "gcc-patches@gcc.gnu.org" <gcc-patches@gcc.gnu.org>
Subject: [committed] [PR other/104044] Remove extraneous semicolons
Date: Sat, 19 Nov 2022 19:26:52 -0700 [thread overview]
Message-ID: <66077669-ff3c-f90a-cd86-eea49878863c@ventanamicro.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 128 bytes --]
As noted in BZ104044 we've got a few places where we have extraneous
semicolons.
Committed as obvious to the trunk,
Jeff
[-- Attachment #2: P --]
[-- Type: text/plain, Size: 2251 bytes --]
commit 6d82e0fea5f988e829912aaa70a9964a81ad4e5e
Author: Jeff Law <jlaw@ventanamicro.com>
Date: Sat Nov 19 19:21:37 2022 -0700
[PR other/104044] Remove extraneous semicolons
gcc/
PR other/104044
* config/mn10300/mn10300.cc (mn10300_print_operand): Remove
extraneous semicolon.
* config/nvptx/nvptx.cc (nvptx_goacc_reduction_fini): Likewise.
gcc/jit/
PR other/104044
* jit-playback.cc (playback::lvale::mark_addressable): Remove
extraeous semicolon
diff --git a/gcc/config/mn10300/mn10300.cc b/gcc/config/mn10300/mn10300.cc
index 2a58dd9256d..f887d9e2808 100644
--- a/gcc/config/mn10300/mn10300.cc
+++ b/gcc/config/mn10300/mn10300.cc
@@ -285,12 +285,12 @@ mn10300_print_operand (FILE *file, rtx x, int code)
REAL_VALUE_TO_TARGET_DOUBLE
(*CONST_DOUBLE_REAL_VALUE (x), val);
fprintf (file, "0x%lx", val[0]);
- break;;
+ break;
case E_SFmode:
REAL_VALUE_TO_TARGET_SINGLE
(*CONST_DOUBLE_REAL_VALUE (x), val[0]);
fprintf (file, "0x%lx", val[0]);
- break;;
+ break;
case E_VOIDmode:
case E_DImode:
mn10300_print_operand_address (file,
@@ -344,7 +344,7 @@ mn10300_print_operand (FILE *file, rtx x, int code)
REAL_VALUE_TO_TARGET_DOUBLE
(*CONST_DOUBLE_REAL_VALUE (x), val);
fprintf (file, "0x%lx", val[1]);
- break;;
+ break;
case E_SFmode:
gcc_unreachable ();
case E_VOIDmode:
diff --git a/gcc/config/nvptx/nvptx.cc b/gcc/config/nvptx/nvptx.cc
index 2fe120b3873..ed3807bee43 100644
--- a/gcc/config/nvptx/nvptx.cc
+++ b/gcc/config/nvptx/nvptx.cc
@@ -7043,7 +7043,7 @@ nvptx_goacc_reduction_fini (gcall *call, offload_attrs *oa)
enum tree_code op
= (enum tree_code)TREE_INT_CST_LOW (gimple_call_arg (call, 4));
gimple_seq seq = NULL;
- tree r = NULL_TREE;;
+ tree r = NULL_TREE;
push_gimplify_context (true);
diff --git a/gcc/jit/jit-playback.cc b/gcc/jit/jit-playback.cc
index bf006903a44..069ed705609 100644
--- a/gcc/jit/jit-playback.cc
+++ b/gcc/jit/jit-playback.cc
@@ -1647,7 +1647,7 @@ bool
playback::lvalue::
mark_addressable (location *loc)
{
- tree x = as_tree ();;
+ tree x = as_tree ();
while (1)
switch (TREE_CODE (x))
reply other threads:[~2022-11-20 2:26 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=66077669-ff3c-f90a-cd86-eea49878863c@ventanamicro.com \
--to=jlaw@ventanamicro.com \
--cc=gcc-patches@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: link
Be 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).