public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "trippels at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug preprocessor/64604] New: [5 Regression] r212194 causes zsh miscompilation Date: Wed, 14 Jan 2015 21:48:00 -0000 [thread overview] Message-ID: <bug-64604-4@http.gcc.gnu.org/bugzilla/> (raw) https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64604 Bug ID: 64604 Summary: [5 Regression] r212194 causes zsh miscompilation Product: gcc Version: 5.0 Status: UNCONFIRMED Severity: normal Priority: P3 Component: preprocessor Assignee: unassigned at gcc dot gnu.org Reporter: trippels at gcc dot gnu.org CC: dodji at gcc dot gnu.org Starting with r212194 zsh gets miscompiled on my machine (x86_64). Symptoms include startup crashes and bizarre tab expansion failures like: markus@x4 ~ % /va<tab> _main_complete:trap:131: undefined signal: INT I haven't looked deeper yet. Will hopefully be able to do so tomorrow.
next reply other threads:[~2015-01-14 21:48 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-01-14 21:48 trippels at gcc dot gnu.org [this message] 2015-01-15 8:13 ` [Bug preprocessor/64604] " trippels at gcc dot gnu.org 2015-01-15 8:15 ` jakub at gcc dot gnu.org 2015-01-15 8:18 ` trippels at gcc dot gnu.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=bug-64604-4@http.gcc.gnu.org/bugzilla/ \ --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).