diff options
author | Chris Metcalf <cmetcalf@tilera.com> | 2014-06-17 17:21:08 +0100 |
---|---|---|
committer | Nick Clifton <nickc@redhat.com> | 2014-06-17 17:21:08 +0100 |
commit | 6d1ace6861e999361b30d1bc27459ab8094e0d4a (patch) | |
tree | 0f2d2bc05ec08a122ca10b1ddcc30cef25021886 /gas/macro.c | |
parent | 548a23572832015e1d457188c5962e349825e86e (diff) | |
download | fsf-binutils-gdb-6d1ace6861e999361b30d1bc27459ab8094e0d4a.zip fsf-binutils-gdb-6d1ace6861e999361b30d1bc27459ab8094e0d4a.tar.gz fsf-binutils-gdb-6d1ace6861e999361b30d1bc27459ab8094e0d4a.tar.bz2 |
This fixes a bug whereby #line directives inside a macro would be ignored,
thus resulting in bad line debug information.
PR gas/16908
* macro.c (buffer_and_nest): Honour #line directives inside
macros.
Diffstat (limited to 'gas/macro.c')
-rw-r--r-- | gas/macro.c | 22 |
1 files changed, 22 insertions, 0 deletions
diff --git a/gas/macro.c b/gas/macro.c index 4589bd8..d3b4e47 100644 --- a/gas/macro.c +++ b/gas/macro.c @@ -211,6 +211,28 @@ buffer_and_nest (const char *from, const char *to, sb *ptr, break; } } + + /* PR gas/16908 + Apply and discard .linefile directives that appear within + the macro. For long macros, one might want to report the + line number information associated with the lines within + the macro definition, but we would need more infrastructure + to make that happen correctly (e.g. resetting the line + number when expanding the macro), and since for short + macros we clearly prefer reporting the point of expansion + anyway, there's not an obviously better fix here. */ + if (strncasecmp (ptr->ptr + i, "linefile", 8) == 0) + { + char *saved_input_line_pointer = input_line_pointer; + char saved_eol_char = ptr->ptr[ptr->len]; + + ptr->ptr[ptr->len] = '\0'; + input_line_pointer = ptr->ptr + i + 8; + s_app_line (0); + ptr->ptr[ptr->len] = saved_eol_char; + input_line_pointer = saved_input_line_pointer; + ptr->len = line_start; + } } /* Add the original end-of-line char to the end and keep running. */ |