public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "steven at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug debug/25468] [4.0/4.1/4.2 Regression] -g makes g++ loop forever Date: Sat, 22 Jul 2006 16:36:00 -0000 [thread overview] Message-ID: <20060722163632.11775.qmail@sourceware.org> (raw) In-Reply-To: <bug-25468-1902@http.gcc.gnu.org/bugzilla/> ------- Comment #5 from steven at gcc dot gnu dot org 2006-07-22 16:36 ------- We do the loop-and-putc thing in ASM_OUTPUT_LIMITED_STRING and in dw2_asm_output_nstring as well. Probably it's best to add some kind of generic "escaped string" print function, something like the one below that I'll try to actually make work: void asm_output_string_with_escapes (const char *str, size_t len, const char escapes[255], const char *escapes_fmt /* e.g. "\\%03o" */ size_t escapes_fmt_len) { size_t i, j, len, escaped_len; char *escaped_str; escaped_len = len; for (i = 0; i < len; i++) { int c = str[i]; if (c == '\"' || c == '\\') escaped_len++; else if (escapes[c]) escaped_len += escapes_fmt_len; } str = xmalloc (escaped_len + 1); for (i = 0, j = 0; i < len; i++) { int c = str[i]; if (!escapes[c]) { if (c == '\"' || c == '\\') escaped_str[j++] = '\\'; escaped_str[j++] = c; } else { /* ??? Must also handle things like \t and \b here. */ snprintf (&escaped_str[j], escapes_fmt_len, escapes_fmt, c); j += escapes_fmt_len; } } escaped_str[j] = '\0'; fputs (escaped_str, asm_out_file); free (escaped_str); } -- steven at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- AssignedTo|unassigned at gcc dot gnu |steven at gcc dot gnu dot |dot org |org Status|NEW |ASSIGNED Last reconfirmed|2006-02-08 04:02:15 |2006-07-22 16:36:32 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=25468
next prev parent reply other threads:[~2006-07-22 16:36 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2005-12-17 22:14 [Bug c++/25468] New: " sylvain dot pion at sophia dot inria dot fr 2005-12-17 22:26 ` [Bug c++/25468] " sylvain dot pion at sophia dot inria dot fr 2005-12-17 23:26 ` [Bug debug/25468] [3.4 Regression] " sylvain dot pion at sophia dot inria dot fr 2005-12-17 23:27 ` pinskia at gcc dot gnu dot org 2006-02-08 4:02 ` wilson at gcc dot gnu dot org 2006-06-04 19:30 ` [Bug debug/25468] [4.0/4.1/4.2 " jsm28 at gcc dot gnu dot org 2006-06-04 19:52 ` mmitchel at gcc dot gnu dot org 2006-07-22 16:36 ` steven at gcc dot gnu dot org [this message] 2006-07-23 11:51 ` steven at gcc dot gnu dot org 2006-07-23 13:11 ` steven at gcc dot gnu dot org 2006-07-23 14:55 ` steven at gcc dot gnu dot org 2006-07-23 17:56 ` steven at gcc dot gnu dot org 2006-07-23 17:57 ` [Bug debug/25468] [4.0/4.1 " steven at gcc dot gnu dot org 2006-07-31 22:09 ` steven at gcc dot gnu dot org 2006-07-31 22:13 ` [Bug debug/25468] [4.0 " pinskia at gcc dot gnu dot org 2006-07-31 22:14 ` steven at gcc dot gnu dot org 2006-07-31 22:14 ` steven at gcc dot gnu dot org 2007-02-03 16:10 ` gdr at gcc dot gnu dot org
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=20060722163632.11775.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=gcc-bugs@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: linkBe 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).