public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: "Joseph S. Myers" <jsm28@cam.ac.uk> To: nobody@gcc.gnu.org Cc: gcc-prs@gcc.gnu.org, Subject: Re: c/9390: Segmentation Fault when compiling for athlon with LANG=es_ES@euro or LC_ALL=es_ES@euro Date: Tue, 04 Feb 2003 23:46:00 -0000 [thread overview] Message-ID: <20030204234600.7726.qmail@sources.redhat.com> (raw) The following reply was made to PR c/9390; it has been noted by GNATS. From: "Joseph S. Myers" <jsm28@cam.ac.uk> To: Wolfgang Bangerth <bangerth@ticam.utexas.edu> Cc: <david@aspl.es>, <gcc-bugs@gcc.gnu.org>, <gcc-gnats@gcc.gnu.org> Subject: Re: c/9390: Segmentation Fault when compiling for athlon with LANG=es_ES@euro or LC_ALL=es_ES@euro Date: Tue, 4 Feb 2003 23:40:53 +0000 (GMT) On Mon, 3 Feb 2003, Wolfgang Bangerth wrote: > I wrote a little script that tried to find these problems. See the thread > that started at > http://gcc.gnu.org/ml/gcc-patches/2002-10/msg01694.html > There's extensive discussion with Zack about the problem and how he thinks > this should be fixed/tackled. I don't see either the script or a list of problems in that thread. The ordering problems do need to wait for GCC to get %1$ support (though having messages with %1$ causing a crash because it isn't supported is no worse than having existing messages with the wrong order causing a crash). > I don't think this was reported to the translation maintainers. I was > fairly new to gcc processes back then. I would appreciate if you could > take the necessary steps. I've committed the current translations, and proposed a patch <http://gcc.gnu.org/ml/gcc-patches/2003-02/msg00245.html> to add documentation about how GCC interacts with the Translation Project and how to contact the language teams (supposing that the script shows such problems still present in the current translations, the reports can be sent to the teams). -- Joseph S. Myers jsm28@cam.ac.uk
next reply other threads:[~2003-02-04 23:46 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-02-04 23:46 Joseph S. Myers [this message] -- strict thread matches above, loose matches on Subject: below -- 2003-02-05 0:06 Wolfgang Bangerth 2003-02-03 16:16 Wolfgang Bangerth 2003-02-03 0:06 Joseph S. Myers 2003-02-02 19:36 Wolfgang Bangerth 2003-02-01 23:36 Joseph S. Myers 2003-02-01 22:16 bangerth 2003-01-21 18:06 david
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=20030204234600.7726.qmail@sources.redhat.com \ --to=jsm28@cam.ac.uk \ --cc=gcc-prs@gcc.gnu.org \ --cc=nobody@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).