public inbox for gcc-bugs@sourceware.org
help / color / mirror / Atom feed
From: "jvdelisle at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: gcc-bugs@gcc.gnu.org
Subject: [Bug target/65810] powerpc64 libgfortran alignment issue?
Date: Mon, 20 Apr 2015 01:43:00 -0000	[thread overview]
Message-ID: <bug-65810-4-SBZrBQ2Oqp@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-65810-4@http.gcc.gnu.org/bugzilla/>

https://gcc.gnu.org/bugzilla/show_bug.cgi?id=65810

Jerry DeLisle <jvdelisle at gcc dot gnu.org> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |jvdelisle at gcc dot gnu.org

--- Comment #1 from Jerry DeLisle <jvdelisle at gcc dot gnu.org> ---
Could you post the output of: gfortran -v so we can confirm the version number.

I am not seeing it show up on any of the automatic testers.  I tried to access
the Power7 machine I usually use and can't get in (comm problems).


  reply	other threads:[~2015-04-20  1:43 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-20  0:10 [Bug target/65810] New: " amodra at gmail dot com
2015-04-20  1:43 ` jvdelisle at gcc dot gnu.org [this message]
2015-04-20  2:15 ` [Bug target/65810] " bergner at gcc dot gnu.org
2015-04-20  3:14 ` amodra at gmail dot com
2015-04-20  5:24 ` amodra at gmail dot com
2015-04-20  9:45 ` [Bug target/65810] powerpc64 alignment of r2 insufficient for loading long-double constants dominiq at lps dot ens.fr
2015-04-20 13:14 ` amodra at gmail dot com
2015-04-28  3:48 ` amodra at gcc dot gnu.org
2015-04-28  3:50 ` amodra at gmail 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-65810-4-SBZrBQ2Oqp@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: 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).