From: Jim Wilson <wilson@tuliptree.org>
To: gcc-patches <gcc-patches@gcc.gnu.org>
Subject: [PATCH 02/13] fix sdbout.c references in xcoffout.c
Date: Wed, 25 Oct 2017 21:31:00 -0000 [thread overview]
Message-ID: <1508967041.2379.21.camel@tuliptree.org> (raw)
In-Reply-To: <1508966659.2379.15.camel@tuliptree.org>
[-- Attachment #1: Type: text/plain, Size: 137 bytes --]
This changes some sdbout.c file references to past tense, since they
are still useful to explain why the code was written this way.
Jim
[-- Attachment #2: Type: text/plain, Size: 1241 bytes --]
gcc/
* xcoffout.c: Refer to former sdbout.c file.
(xcoffout_begin_prologue): Use past tense for sdbout.c reference.
---
gcc/xcoffout.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/gcc/xcoffout.c b/gcc/xcoffout.c
index 17b201a..cf2064d 100644
--- a/gcc/xcoffout.c
+++ b/gcc/xcoffout.c
@@ -20,7 +20,7 @@ along with GCC; see the file COPYING3. If not see
/* Output xcoff-format symbol table data. The main functionality is contained
in dbxout.c. This file implements the sdbout-like parts of the xcoff
interface. Many functions are very similar to their counterparts in
- sdbout.c. */
+ the former sdbout.c file. */
#include "config.h"
#include "system.h"
@@ -452,7 +452,7 @@ xcoffout_begin_prologue (unsigned int line,
ASM_OUTPUT_LFB (asm_out_file, line);
dbxout_parms (DECL_ARGUMENTS (current_function_decl));
- /* Emit the symbols for the outermost BLOCK's variables. sdbout.c does this
+ /* Emit the symbols for the outermost BLOCK's variables. sdbout.c did this
in sdbout_begin_block, but there is no guarantee that there will be any
inner block 1, so we must do it here. This gives a result similar to
dbxout, so it does make some sense. */
--
2.7.4
next prev parent reply other threads:[~2017-10-25 21:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-25 21:28 [PATCH 00/13] Removal of SDB debug info support Jim Wilson
2017-10-25 21:30 ` [PATCH 01/13] remove sdbout.h and associated code Jim Wilson
2017-10-25 22:46 ` Jim Wilson
2017-10-25 21:31 ` Jim Wilson [this message]
2017-10-25 21:36 ` [PATCH 03/13] drop TYPE_SYMTAB_POINTER Jim Wilson
2017-10-25 21:36 ` [PATCH 04/13] Delete the sdbout files Jim Wilson
2017-10-25 21:45 ` [PATCH 05/13] remove sdb/coff info from docs Jim Wilson
2017-10-25 21:48 ` [PATCH 06/13] remove sdb and -gcoff from non-target files Jim Wilson
2017-10-26 9:57 ` Richard Biener
2017-10-26 22:13 ` Jim Wilson
2017-10-27 8:46 ` Richard Biener
2017-10-29 23:12 ` Jim Wilson
2017-10-25 21:51 ` [PATCH 07/13] fix testsuite debug torture lists Jim Wilson
2017-10-25 21:52 ` [PATCH 08/13] fix dbxcoff.h Jim Wilson
2017-10-25 21:53 ` [PATCH 09/13] fix vxworks file Jim Wilson
2017-10-25 22:00 ` [PATCH 11/13] drop sdb references in target comments copied from docs Jim Wilson
2017-10-25 22:00 ` [PATCH 10/13] fix i386 files Jim Wilson
2017-10-25 22:03 ` [PATCH 12/13] fix m68k files Jim Wilson
2017-10-25 22:07 ` [PATCH 13/13] fix MIPS files Jim Wilson
2017-10-29 10:46 ` Matthew Fortune
2017-10-26 9:39 ` [PATCH 00/13] Removal of SDB debug info support Richard Biener
2017-10-26 14:07 ` Jeff Law
2017-10-30 1:41 ` Jim Wilson
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=1508967041.2379.21.camel@tuliptree.org \
--to=wilson@tuliptree.org \
--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).