From: Richard Sandiford <richard.sandiford@linaro.org>
To: Alexandre Oliva <aoliva@redhat.com>
Cc: Jakub Jelinek <jakub@redhat.com>,
Jason Merrill <jason@redhat.com>, Jeff Law <law@redhat.com>,
Richard Biener <richard.guenther@gmail.com>,
gcc-patches <gcc-patches@gcc.gnu.org>
Subject: Re: [SFN+LVU+IEPM v4 7/9] [LVU] Introduce location views
Date: Tue, 30 Jan 2018 22:11:00 -0000 [thread overview]
Message-ID: <87tvv3gj9b.fsf@linaro.org> (raw)
In-Reply-To: <orh8r3rzxm.fsf@lxoliva.fsfla.org> (Alexandre Oliva's message of "Tue, 30 Jan 2018 15:58:45 -0200")
Alexandre Oliva <aoliva@redhat.com> writes:
> On Jan 26, 2018, Jakub Jelinek <jakub@redhat.com> wrote:
>
>> Having to tweak debug info consumers so that they treat DW_LLE_* of 9
>> one way for .debug_loclist of version 5 and another way for .debug_loclist
>> of version 6 isn't a good idea.
>
> Maybe we don't have to do that. The reason I implemented the proposed
> format was to have a reference implementation, but since it's an
> extension to a non-extensible part of DWARF5, it's hard to justify
> consumer implementations for that.
>
>> Why don't you emit the DW_LLE_GNU_view_pair stuff in .debug_loclists
>> already with -gdwarf-5, if needed paired without some TU attribute that says
>> that views are emitted?
>
> Because that would make the loclists unreadable for any DWARF5-compliant
> consumer.
>
>
>> Haven't looked for it it in the coding standards, but it is something
>> I've been asked to do in my code by various reviewers over the years and
>> what I've been asking others in my patch reviews from others too.
>
> Thanks. It was the first (well, second; you'd requested similar changes
> another time before) I heard of that. I'm still unconvinced the way I
> used is not compliant, but I'll keep that in mind. Hopefully I won't
> run into someone who insists the other one (the one you reject) is the
> only correct one ;-)
>
>> I feel strongly about indenting stuff right,
>
> I'm with you on that, we just have different ideas about what "right"
> stands for ;-)
>
>> which if it wouldn't fit would be
>> return verylongcondition____________________________________
>> && otherlongcondition__________________________________;
>> rather than
>> return verylongcondition____________________________________
>> && otherlongcondition__________________________________;
>> or similar, it would surprise me if it is not in the coding standard.
>
> I agree neither of these two forms is correct.
>
> But it is my understanding that both of the following are correct:
>
> return (verylongcondition____________________________________
> && otherlongcondition__________________________________);
>
> return verylongcondition____________________________________
> && otherlongcondition__________________________________;
>
> The first, because the parenthesized expression is continued with
> indentation to match the parenthesis, the second because the return
> statement is continued with the correct indentation for the continuation
> of a statement.
Thought it had to be the first. When they talk about indenting leading
operators, the conventions say:
Insert extra parentheses so that Emacs will indent the code properly.
which at least implies that not inserting parantheses and indenting by
two spaces isn't "properly".
And I think most GCC code does stick to that (i.e. use the bracketed form).
Thanks,
Richard
next prev parent reply other threads:[~2018-01-30 20:54 UTC|newest]
Thread overview: 156+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-05 23:21 Introduce Statement Frontier Notes and Location Views Alexandre Oliva
2017-07-13 13:17 ` Alexandre Oliva
2017-08-18 22:49 ` Statement Frontier Notes, Location Views, and Inlined Entry Point Markers (was: Re: Introduce Statement Frontier Notes and Location Views) Alexandre Oliva
2017-08-21 12:35 ` Richard Biener
2017-08-22 22:44 ` Statement Frontier Notes, Location Views, and Inlined Entry Point Markers Alexandre Oliva
2017-08-23 12:33 ` Richard Biener
2017-08-25 16:41 ` Alexandre Oliva
2017-09-07 21:44 ` Joseph Myers
2017-09-21 2:24 ` Alexandre Oliva
2017-08-22 22:44 ` Alexandre Oliva
2017-08-23 12:12 ` Richard Biener
2017-08-25 15:26 ` Alexandre Oliva
2017-08-28 12:41 ` Richard Biener
2017-08-25 19:22 ` Alexandre Oliva
2017-09-01 1:07 ` Alexandre Oliva
2017-09-01 1:15 ` [PATCH 2/9] [SFN] boilerplate changes in preparation to introduce nonbind markers Alexandre Oliva
2017-09-01 1:15 ` [PATCH 1/9] [SFN] adjust RTL insn-walking API Alexandre Oliva
2017-09-01 1:15 ` [PATCH 5/9] [SFN] Introduce -gstatement-frontiers option, enable debug markers Alexandre Oliva
2017-09-01 1:16 ` [PATCH 7/9] [LVU] Introduce location views Alexandre Oliva
2017-09-01 1:16 ` [PATCH 6/9] [LVU] Allow final_start_function to skip initial insns Alexandre Oliva
2017-09-01 1:16 ` [PATCH 9/9] [IEPM] Introduce inline entry point markers Alexandre Oliva
2017-09-01 1:16 ` [PATCH 3/9] [SFN] not-quite-boilerplate changes in preparation to introduce nonbind markers Alexandre Oliva
2017-09-01 1:16 ` [PATCH 4/9] [SFN] introduce statement frontier notes, still disabled Alexandre Oliva
2017-09-01 1:16 ` [PATCH 8/9] [IEPM] Introduce debug hook for inline entry point markers Alexandre Oliva
2017-09-30 9:04 ` Statement Frontier Notes, Location Views, and Inlined Entry Point Markers Alexandre Oliva
2017-09-30 9:09 ` [PATCH 6/9] [LVU] Allow final_start_function to skip initial insns Alexandre Oliva
2017-10-19 11:07 ` Richard Biener
2017-10-31 5:10 ` Jeff Law
2017-10-31 5:23 ` Jeff Law
2017-11-01 18:20 ` Alexandre Oliva
2017-11-02 13:00 ` Richard Biener
2017-09-30 9:09 ` [PATCH 4/9] [SFN] introduce statement frontier notes, still disabled Alexandre Oliva
2017-10-09 13:11 ` Richard Biener
2017-10-13 7:25 ` Alexandre Oliva
2017-10-13 9:41 ` Richard Biener
2017-10-17 22:06 ` Alexandre Oliva
2017-10-24 18:11 ` Jason Merrill
2017-11-01 19:14 ` Alexandre Oliva
2017-11-01 19:49 ` Jason Merrill
2017-09-30 9:09 ` [PATCH 2/9] [SFN] boilerplate changes in preparation to introduce nonbind markers Alexandre Oliva
2017-10-09 13:02 ` Richard Biener
2017-09-30 9:09 ` [PATCH 5/9] [SFN] Introduce -gstatement-frontiers option, enable debug markers Alexandre Oliva
2017-10-09 13:12 ` Richard Biener
2017-09-30 9:09 ` [PATCH 1/9] [SFN] adjust RTL insn-walking API Alexandre Oliva
2017-10-09 13:24 ` Richard Biener
2017-09-30 9:10 ` [PATCH 7/9] [LVU] Introduce location views Alexandre Oliva
2017-09-30 9:10 ` [PATCH 9/9] [IEPM] Introduce inline entry point markers Alexandre Oliva
2017-10-31 6:22 ` Jeff Law
2017-11-01 18:36 ` Alexandre Oliva
2017-11-09 16:30 ` Jeff Law
2017-11-10 2:31 ` Alexandre Oliva
2017-09-30 9:10 ` [PATCH 8/9] [IEPM] Introduce debug hook for " Alexandre Oliva
2017-10-31 5:58 ` Jeff Law
2017-09-30 9:10 ` [PATCH 3/9] [SFN] not-quite-boilerplate changes in preparation to introduce nonbind markers Alexandre Oliva
2017-10-09 13:07 ` Richard Biener
2017-11-10 2:36 ` SFN+LVU+IEPM v4 (was: Re: Statement Frontier Notes, Location Views, and Inlined Entry Point Markers) Alexandre Oliva
2017-11-10 2:36 ` [SFN+LVU+IEPM v4 3/9] [SFN] not-quite-boilerplate changes in preparation to introduce nonbind markers Alexandre Oliva
2017-12-07 22:44 ` Jeff Law
2017-12-12 2:31 ` Alexandre Oliva
2017-11-10 2:36 ` [SFN+LVU+IEPM v4 6/9] [SFN] Introduce -gstatement-frontiers option, enable debug markers Alexandre Oliva
2017-12-07 22:49 ` Jeff Law
2017-12-12 2:42 ` Alexandre Oliva
2017-12-12 9:16 ` Christophe Lyon
2017-12-13 4:22 ` Alexandre Oliva
2018-01-07 17:48 ` H.J. Lu
2017-12-27 8:00 ` [nvptx, committed] Disable -gstatement-frontiers for nvptx Tom de Vries
2017-12-29 4:12 ` Alexandre Oliva
2017-12-29 11:42 ` Tom de Vries
2017-12-31 20:05 ` Alexandre Oliva
2018-01-11 10:12 ` Tom de Vries
2017-11-10 2:36 ` [SFN+LVU+IEPM v4 2/9] [SFN] boilerplate changes in preparation to introduce nonbind markers Alexandre Oliva
2017-12-07 22:27 ` Jeff Law
2017-12-12 2:55 ` Alexandre Oliva
2017-11-10 2:36 ` [SFN+LVU+IEPM v4 4/9] [SFN] stabilize find_bb_boundaries Alexandre Oliva
2017-12-07 22:46 ` Jeff Law
2017-12-12 2:38 ` Alexandre Oliva
2017-11-10 2:36 ` [SFN+LVU+IEPM v4 5/9] [SFN] introduce statement frontier notes, still disabled Alexandre Oliva
2017-12-07 23:59 ` Jeff Law
2017-12-12 2:41 ` Alexandre Oliva
2017-11-10 2:36 ` [SFN+LVU+IEPM v4 1/9] [SFN] adjust RTL insn-walking API Alexandre Oliva
2017-12-07 22:25 ` Jeff Law
2017-12-12 3:10 ` Alexandre Oliva
2017-12-14 11:55 ` Alexandre Oliva
2017-12-14 12:07 ` Jakub Jelinek
2017-12-14 18:25 ` Alexandre Oliva
2017-11-10 2:37 ` [SFN+LVU+IEPM v4 8/9] [IEPM] Introduce debug hook for inline entry point markers Alexandre Oliva
2017-12-07 22:51 ` Jeff Law
2017-12-12 2:44 ` Alexandre Oliva
2017-11-10 5:05 ` [SFN+LVU+IEPM v4 7/9] [LVU] Introduce location views Alexandre Oliva
2017-11-13 10:18 ` Richard Biener
2017-11-15 3:59 ` Alexandre Oliva
2017-12-11 23:12 ` Jeff Law
2017-12-12 2:52 ` Alexandre Oliva
2018-01-24 17:36 ` Jakub Jelinek
2018-01-25 20:19 ` Alexandre Oliva
2018-01-26 14:58 ` Jakub Jelinek
2018-01-30 18:40 ` Alexandre Oliva
2018-01-30 22:11 ` Richard Sandiford [this message]
2018-02-07 4:14 ` Alexandre Oliva
2018-02-07 7:43 ` Alexandre Oliva
2018-02-06 21:13 ` Jason Merrill
2018-02-07 4:02 ` Alexandre Oliva
2018-02-07 19:23 ` Jason Merrill
2018-02-08 12:56 ` Alexandre Oliva
2018-02-08 16:05 ` Jason Merrill
2018-02-09 3:49 ` Alexandre Oliva
2018-02-07 7:35 ` Alexandre Oliva
2018-02-07 7:36 ` Alexandre Oliva
2018-02-08 19:58 ` Jason Merrill
2018-02-09 3:20 ` Alexandre Oliva
2018-02-11 19:04 ` Andreas Schwab
2018-02-11 20:47 ` Andreas Schwab
2018-02-12 7:46 ` Alexandre Oliva
2018-02-12 7:49 ` Alexandre Oliva
2018-02-12 10:11 ` Andreas Schwab
2018-02-13 5:47 ` Alexandre Oliva
2018-02-14 9:23 ` Andreas Schwab
2017-11-10 5:29 ` [SFN+LVU+IEPM v4 9/9] [IEPM] Introduce inline entry point markers Alexandre Oliva
2017-12-12 2:54 ` Alexandre Oliva
2017-12-21 5:18 ` Jeff Law
2018-01-24 7:11 ` Alexandre Oliva
2018-01-24 17:40 ` Jakub Jelinek
2018-01-25 20:14 ` Alexandre Oliva
2018-02-09 3:21 ` Alexandre Oliva
2018-02-09 3:53 ` Alan Modra
2018-02-09 4:13 ` Jeff Law
2018-02-09 10:35 ` Alexandre Oliva
2018-02-09 12:10 ` Alan Modra
2018-02-09 15:09 ` Jeff Law
2018-02-09 22:52 ` Joseph Myers
2018-02-10 1:36 ` Joseph Myers
2018-02-10 12:35 ` Alexandre Oliva
2018-02-10 18:19 ` Jeff Law
2018-02-11 15:29 ` Alexandre Oliva
2018-02-09 21:01 ` Alexandre Oliva
2018-02-09 23:49 ` Jakub Jelinek
2018-02-10 0:56 ` Alexandre Oliva
2018-02-12 8:08 ` Alexandre Oliva
2018-02-13 13:52 ` Alexandre Oliva
2018-02-13 16:15 ` Jeff Law
2018-02-15 15:23 ` Szabolcs Nagy
2018-02-21 10:12 ` Alexandre Oliva
2018-02-21 12:08 ` Uros Bizjak
2018-02-22 15:22 ` Szabolcs Nagy
2018-02-28 6:17 ` Alexandre Oliva
2018-03-09 9:49 ` Bin.Cheng
2018-03-09 9:55 ` Ramana Radhakrishnan
2018-03-09 11:35 ` Jakub Jelinek
2018-03-07 19:43 ` Jeff Law
2018-02-10 4:39 ` Alexandre Oliva
2018-02-10 6:35 ` Jeff Law
2018-02-10 13:05 ` Alexandre Oliva
2018-02-10 16:36 ` Jeff Law
2018-02-21 10:33 ` Alexandre Oliva
2018-02-26 12:47 ` Richard Biener
2017-11-10 21:31 ` SFN+LVU+IEPM v4 Alexandre Oliva
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=87tvv3gj9b.fsf@linaro.org \
--to=richard.sandiford@linaro.org \
--cc=aoliva@redhat.com \
--cc=gcc-patches@gcc.gnu.org \
--cc=jakub@redhat.com \
--cc=jason@redhat.com \
--cc=law@redhat.com \
--cc=richard.guenther@gmail.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).