From: "neleai at seznam dot cz" <sourceware-bugzilla@sourceware.org>
To: libc-locales@sourceware.org
Subject: [Bug localedata/15870] backtrace don't give same result when called between redhat-32bit and redhat-64bit
Date: Mon, 14 Oct 2013 10:12:00 -0000 [thread overview]
Message-ID: <bug-15870-716-w6QVqOUFOj@http.sourceware.org/bugzilla/> (raw)
In-Reply-To: <bug-15870-716@http.sourceware.org/bugzilla/>
https://sourceware.org/bugzilla/show_bug.cgi?id=15870
Ondrej Bilka <neleai at seznam dot cz> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
CC| |neleai at seznam dot cz
Resolution|--- |INVALID
--- Comment #1 from Ondrej Bilka <neleai at seznam dot cz> ---
A optimizing compiler can inline/reorder code so line where error appears may
move. There is nothing that we can do with this.
--
You are receiving this mail because:
You are on the CC list for the bug.
next prev parent reply other threads:[~2013-10-14 10:12 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-21 3:05 [Bug localedata/15870] New: " stigano at 163 dot com
2013-08-21 3:05 ` [Bug localedata/15870] " stigano at 163 dot com
2013-10-14 10:12 ` neleai at seznam dot cz [this message]
2014-06-13 13:17 ` fweimer at redhat dot com
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-15870-716-w6QVqOUFOj@http.sourceware.org/bugzilla/ \
--to=sourceware-bugzilla@sourceware.org \
--cc=libc-locales@sourceware.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).