From: Mark Wielaard <mjw@redhat.com>
To: Simon Marchi <simon.marchi@ericsson.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix GCC6 -Wmisleading-indentation issues.
Date: Mon, 25 Jan 2016 22:14:00 -0000 [thread overview]
Message-ID: <20160125221411.GA2721@blokker.redhat.com> (raw)
In-Reply-To: <56A697A2.9060207@ericsson.com>
On Mon, Jan 25, 2016 at 04:46:10PM -0500, Simon Marchi wrote:
> If you feel like it, you could build with --enable-targets=all to
> enable more code.
> You'll find more of these.
Thanks, but honestly this was just inspired by my desire to get
a local build with gcc6 going. It would be good to build more code
with GCC6 of course. I am sure it will find interesting issues.
> One little comment below, otherwise it LGTM (without implying that my voice is
> worth anything).
>
> > diff --git a/gdb/inflow.c b/gdb/inflow.c
> > index bbd2b12..d1dd41c 100644
> > --- a/gdb/inflow.c
> > +++ b/gdb/inflow.c
> > @@ -413,7 +413,7 @@ child_terminal_ours_1 (int output_only)
> > if (tinfo->run_terminal != NULL || gdb_has_a_terminal () == 0)
> > return;
> >
> > - {
> > + {
> > #ifdef SIGTTOU
> > /* Ignore this signal since it will happen when we try to set the
> > pgrp. */
> > @@ -497,7 +497,7 @@ child_terminal_ours_1 (int output_only)
> > result = fcntl (0, F_SETFL, our_terminal_info.tflags);
> > result = fcntl (0, F_SETFL, our_terminal_info.tflags);
> > #endif
> > - }
> > + }
>
> Shouldn't the code inside the brackets be de-indented too?
Possibly. Or remove the whole block and move stuff into the outer scope
now that it isn't strictly needed. But both create lots of code movement
because of the peculiar ifdefs in this code. And it clearly wasn't the
intention of the original author that removed the if statement in
commit d9d2d8b.
Thanks,
Mark
next prev parent reply other threads:[~2016-01-25 22:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-25 19:41 Mark Wielaard
2016-01-25 21:46 ` Simon Marchi
2016-01-25 22:14 ` Mark Wielaard [this message]
2016-01-25 22:24 ` Pedro Alves
2016-01-25 22:38 ` Mark Wielaard
2016-01-25 23:00 ` Pedro Alves
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=20160125221411.GA2721@blokker.redhat.com \
--to=mjw@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=simon.marchi@ericsson.com \
/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