From: Jan Kratochvil <jan.kratochvil@redhat.com>
To: Ondrej Oprala <ooprala@redhat.com>
Cc: gdb-patches@sourceware.org, Tom Tromey <tromey@redhat.com>
Subject: Re: [PATCH 02/18] poison "new"
Date: Thu, 10 Oct 2013 19:15:00 -0000 [thread overview]
Message-ID: <20131010191458.GA14000@host2.jankratochvil.net> (raw)
In-Reply-To: <1381339053-14519-3-git-send-email-ooprala@redhat.com>
On Wed, 09 Oct 2013 19:17:17 +0200, Ondrej Oprala wrote:
> --- a/gdb/ChangeLog
> +++ b/gdb/ChangeLog
> @@ -22,6 +22,43 @@
>
> 2013-10-09 Tom Tromey <tromey@redhat.com>
>
> + * bcache.c (new_bstr) : Renamed from new.
> + * buildsym.c(new_ctx) : Likewise.
> + * cleanups.c(new_cleanup) : Likewise.
Besides Pedro's comment on formatting of the ChangeLog entry do not post
ChangeLog entry already modified in the file. Post it only as a preceding
text (commit message). You can see here the entry is wrongly placed, new
entry should be always at the top of the file. Besides that it always causes
patch or merge conflicts as the top of ChangeLog files is continually
changing.
[...]
> --- a/gdb/dbxread.c
> +++ b/gdb/dbxread.c
[...]
> @@ -2799,16 +2799,17 @@ process_one_symbol (int type, int desc, CORE_ADDR valu, char *name,
> }
>
> within_function = 0;
> - new = pop_context ();
> + new_ctx = pop_context ();
>
> /* Make a block for the local symbols within. */
> - block = finish_block (new->name, &local_symbols, new->old_blocks,
> - new->start_addr, new->start_addr + valu,
> + block = finish_block (new_ctx->name, &local_symbols,
> + new_ctx->old_blocks,
> + new_ctx->start_addr, new_ctx->start_addr + valu,
> objfile);
>
> /* For C++, set the block's scope. */
> - if (SYMBOL_LANGUAGE (new->name) == language_cplus)
> - cp_set_block_scope (new->name, block, &objfile->objfile_obstack);
> + if (SYMBOL_LANGUAGE (new_ctx->name) == language_cplus)
> + cp_set_block_scope (new_ctx->name, block, &objfile->objfile_obstack);
Line exceeds 80 columns.
>
> /* May be switching to an assembler file which may not be using
> block relative stabs, so reset the offset. */
[...]
> --- a/gdb/dwarf2read.c
> +++ b/gdb/dwarf2read.c
[...]
> @@ -11030,12 +11030,12 @@ read_lexical_block_scope (struct die_info *die, struct dwarf2_cu *cu)
> child_die = sibling_die (child_die);
> }
> }
> - new = pop_context ();
> + new_ctx = pop_context ();
>
> if (local_symbols != NULL || using_directives != NULL)
> {
> struct block *block
> - = finish_block (0, &local_symbols, new->old_blocks, new->start_addr,
> + = finish_block (0, &local_symbols, new_ctx->old_blocks, new_ctx->start_addr,
Line exceeds 80 columns.
> highpc, objfile);
>
> /* Note that recording ranges after traversing children, as we
[...]
> --- a/gdb/stabsread.c
> +++ b/gdb/stabsread.c
[...]
> @@ -3184,7 +3184,7 @@ read_baseclasses (struct field_info *fip, char **pp, struct type *type,
> corresponding to this baseclass. Always zero in the absence of
> multiple inheritance. */
>
> - SET_FIELD_BITPOS (new->field, read_huge_number (pp, ',', &nbits, 0));
> + SET_FIELD_BITPOS (new_fields->field, read_huge_number (pp, ',', &nbits, 0));
Line exceeds 80 columns.
> if (nbits != 0)
> return 0;
> }
Otherwise the patch is fine with me. Please repost it to recheck the proper
GNU Coding Standards formatting of the long lines and the ChangeLog entry.
Ondrej is covered by the Red Hat copyright assignment. I guess you do not
have read/write access to the repository so I can do the check-in of some your
first patches.
Thanks,
Jan
next prev parent reply other threads:[~2013-10-10 19:15 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-09 17:17 [PATCH 00/18] -Wc++-compat patches Ondrej Oprala
2013-10-09 17:17 ` [PATCH 03/18] poison "this" Ondrej Oprala
2013-10-09 17:25 ` Tom Tromey
2013-10-10 12:25 ` Pedro Alves
2013-10-09 17:17 ` [PATCH 01/18] poison "class" Ondrej Oprala
2013-10-09 21:45 ` Stan Shebs
2013-10-20 19:13 ` Mark Kettenis
2013-10-24 17:57 ` Joel Brobecker
2013-10-24 18:21 ` Stan Shebs
2013-10-09 17:17 ` [PATCH 02/18] poison "new" Ondrej Oprala
2013-10-10 12:23 ` Pedro Alves
2013-10-10 19:15 ` Jan Kratochvil [this message]
2013-10-09 17:18 ` [PATCH 18/18] un-nest enum pvk Ondrej Oprala
2013-10-13 17:37 ` Jan Kratochvil
2013-10-09 17:18 ` [PATCH 17/18] fix gdbarch buglet Ondrej Oprala
2013-10-13 17:35 ` Jan Kratochvil
2013-10-09 17:18 ` [PATCH 06/18] poison "delete" Ondrej Oprala
2013-10-13 16:47 ` Jan Kratochvil
2013-10-09 17:18 ` [PATCH 04/18] poison "public" Ondrej Oprala
2013-10-13 16:39 ` Jan Kratochvil
2013-10-09 17:18 ` [PATCH 10/18] poison "operator" Ondrej Oprala
2013-10-13 17:20 ` Jan Kratochvil
2013-10-09 17:18 ` [PATCH 15/18] fix up vec Ondrej Oprala
2013-10-13 17:29 ` Jan Kratochvil
2013-10-09 17:18 ` [PATCH 07/18] poison "explicit" Ondrej Oprala
2013-10-13 16:58 ` Jan Kratochvil
2013-10-09 17:18 ` [PATCH 13/18] poison "typename" Ondrej Oprala
2013-10-13 17:24 ` Jan Kratochvil
2013-10-09 17:18 ` [PATCH 09/18] poison "namespace" Ondrej Oprala
2013-10-13 17:18 ` Jan Kratochvil
2013-10-09 17:18 ` [PATCH 16/18] fix up gdbtypes.h Ondrej Oprala
2013-10-13 17:32 ` Jan Kratochvil
2013-10-09 17:18 ` [PATCH 14/18] poison "using" Ondrej Oprala
2013-10-13 17:25 ` Jan Kratochvil
2013-10-09 17:18 ` [PATCH 11/18] poison "template" Ondrej Oprala
2013-10-13 17:21 ` Jan Kratochvil
2013-10-09 17:18 ` [PATCH 12/18] poison "try" Ondrej Oprala
2013-10-13 17:22 ` Jan Kratochvil
2013-10-09 17:53 ` [PATCH 08/18] poison "mutable" Ondrej Oprala
2013-10-13 17:00 ` Jan Kratochvil
2013-10-13 17:16 ` Jan Kratochvil
2013-10-09 18:09 ` [PATCH 05/18] poison "private" Ondrej Oprala
2013-10-13 16:45 ` Jan Kratochvil
2013-10-14 8:49 ` Pedro Alves
2013-10-14 15:36 ` Tom Tromey
2013-10-14 16:19 ` Pedro Alves
2013-10-09 18:56 ` [PATCH 00/18] -Wc++-compat patches Tom Tromey
2013-10-09 19:43 ` Ondrej Oprala
2013-10-21 15:37 [PATCH 00/18] -Wc++-compat patches v2.0 Ondrej Oprala
2013-10-21 15:37 ` [PATCH 02/18] poison "new" Ondrej Oprala
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=20131010191458.GA14000@host2.jankratochvil.net \
--to=jan.kratochvil@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=ooprala@redhat.com \
--cc=tromey@redhat.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