public inbox for gcc-bugs@sourceware.org help / color / mirror / Atom feed
From: "aoliva at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org> To: gcc-bugs@gcc.gnu.org Subject: [Bug middle-end/67295] [ARM][6 Regression] FAIL: gcc.target/arm/builtin-bswap-1.c scan-assembler-times revshne\\t 1 Date: Wed, 02 Sep 2015 05:55:00 -0000 [thread overview] Message-ID: <bug-67295-4-fpIcAqDp4j@http.gcc.gnu.org/bugzilla/> (raw) In-Reply-To: <bug-67295-4@http.gcc.gnu.org/bugzilla/> https://gcc.gnu.org/bugzilla/show_bug.cgi?id=67295 --- Comment #3 from Alexandre Oliva <aoliva at gcc dot gnu.org> --- Still no luck on a x86_64-linux-gnu build machine, running ../configure --target=arm-none-eabi --disable-shared --disable-nls --disable-threads --disable-tls --enable-checking=yes --enable-languages=c,c++,fortran --with-newlib --with-fpu=neon-fp-armv8 --with-arch=armv8-a --without-isl building binutils (+gdb commit db1ff28b60) and newlib (+cygwin commit c7806ef76a) on the same tree. I'm afraid this is going to be very hard to debug if I can't duplicate it. Any chance you could build a toolchain that works on some machine on the gcc build farm, so that I could get access to it as well and debug from there, or at least try to figure out what the differences are between our setups? Thanks,
prev parent reply other threads:[~2015-09-02 5:55 UTC|newest] Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-08-20 14:00 [Bug middle-end/67295] New: " ktkachov at gcc dot gnu.org 2015-08-21 9:03 ` [Bug middle-end/67295] " rguenth at gcc dot gnu.org 2015-08-21 19:48 ` aoliva at gcc dot gnu.org 2015-09-01 14:15 ` ktkachov at gcc dot gnu.org 2015-09-02 5:55 ` aoliva at gcc dot gnu.org [this message]
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-67295-4-fpIcAqDp4j@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).