From: Bryan Hundven <bryanhundven@gmail.com>
To: Dan Wilder <Dan.Wilder@watchguard.com>
Cc: "crossgcc@sourceware.org" <crossgcc@sourceware.org>
Subject: Re: Announce: Revisiting Patchwork (aka, if you have a patch in patchwork, your attention is ***required***!)
Date: Fri, 05 Dec 2014 02:01:00 -0000 [thread overview]
Message-ID: <CAJ+oik06Qs0fg9hURxA7r6GB3LgaU8aT+5A_rXXAkEvO9ahhQQ@mail.gmail.com> (raw)
In-Reply-To: <13D890DAAABFB44887D834721D06CF4B0161C31B72@mbx1.wgti.net>
Dan,
On Thu, Dec 4, 2014 at 5:46 PM, Dan Wilder <Dan.Wilder@watchguard.com> wrote:
> Thanks Bryan. Yup their backtraces look just like mine.
:)
> I'll keep an eye on that bug, if somebody fixes it before I get a Round Tuit that'd be nice for me! Otherwise I guess the patch goes upstream.
Indeed. You can always add yourself to "cc" on the bug. I saw some
other related bugs in my search, though they are "AIX"... that is
still "powerpc" (rs6000).
Also, Check the patches in comment #4.
As a related... but slightly off-topic thought... Another thing I'd
like to change about crosstool-ng: I dislike all these "for upstream"
patches we harbor in patches/. Maybe I'll work on a RFC on how we can
deal with them.
Cheers,
-Bryan
> --
> Dan Wilder
> ________________________________________
> From: Bryan Hundven [bryanhundven@gmail.com]
> Sent: Thursday, December 04, 2014 5:42 PM
> To: Dan Wilder
> Cc: crossgcc@sourceware.org
> Subject: Re: Announce: Revisiting Patchwork (aka, if you have a patch in patchwork, your attention is ***required***!)
>
> Dan,
>
> On Thu, Dec 4, 2014 at 4:24 PM, Dan Wilder <Dan.Wilder@watchguard.com> wrote:
>> Any unwind patches for ppc in glibc-2.19?
>
> I don't see any in patchwork.
>
>> A small c++ program fails nicely on 32-bit ppc:
>> ------------------------------------------------------------------------------------------
>> #include <iostream>
>>
>> static void cause_exn(void)
>> {
>> std::cout << "cause_exn invoked" << std::endl;
>> throw 20;
>> std::cout << "cause_exn done" << std::endl;
>> }
>>
>> int main(int argc, char **argv)
>> {
>> std::cout << "Starting" << std::endl;
>> try {
>> cause_exn();
>> } catch (int e) {
>> std::cout << "Caught exception " << e << std::endl;
>> }
>> std::cout << "Exiting" << std::endl;
>> return 0;
>> }
>> -----------------------------------------------------------------------------------------------
>>
>> Expected output is:
>>
>> Starting
>> cause_exn invoked
>> Caught exception 20
>> Exiting
>>
>> on 32-bit ppc with glibc-2.19/gcc-4.8.3:
>>
>> Starting
>> cause_exn invoked
>> Aborted (core dumped)
>>
>> Have done some preliminary work and will have a patch for the list in a few weeks, but it would be a shame if somebody else has already gone there!
>
> Have you checked upstream?
> https://sourceware.org/git/?p=glibc.git;a=shortlog;h=refs/heads/master
>
>> ppc_64 works fine. As does x86, x86_64 on the same test program.
>
> Hrm...
> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=62231
> Related?
>
>> --
>> Dan Wilder
>> Btw thanks Bryan for taking the cross-gcc helm and thanks Yann for the excellent work!
>
> :)
>
>>
>>
>> --
>> For unsubscribe information see http://sourceware.org/lists.html#faq
>>
>
> Cheers,
>
> -Bryan
--
For unsubscribe information see http://sourceware.org/lists.html#faq
next prev parent reply other threads:[~2014-12-05 2:01 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-04 23:47 Bryan Hundven
2014-12-05 0:24 ` Dan Wilder
2014-12-05 1:42 ` Bryan Hundven
2014-12-05 1:46 ` Dan Wilder
2014-12-05 2:01 ` Bryan Hundven [this message]
2014-12-16 0:43 ` Dan Wilder
2014-12-16 2:07 ` Bryan Hundven
2014-12-16 4:09 ` Dan Wilder
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=CAJ+oik06Qs0fg9hURxA7r6GB3LgaU8aT+5A_rXXAkEvO9ahhQQ@mail.gmail.com \
--to=bryanhundven@gmail.com \
--cc=Dan.Wilder@watchguard.com \
--cc=crossgcc@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).