public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "amodra at gmail dot com" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug libgcj/57074] gcc-4.8.0 libgcj regression on 32bit Power architecture
Date: Thu, 02 May 2013 23:04:00 -0000	[thread overview]
Message-ID: <bug-57074-8172-gOp5kuKA0s@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-57074-8172@http.gcc.gnu.org/bugzilla/>


http://gcc.gnu.org/bugzilla/show_bug.cgi?id=57074

Alan Modra <amodra at gmail dot com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
   Target Milestone|4.8.1                       |---

--- Comment #10 from Alan Modra <amodra at gmail dot com> 2013-05-02 23:04:37 UTC ---
Another fairly easy fix is to make output_object_block() emit the .align
directives instead of padding.  Yes, this covers up the real bug that Jakub has
been looking at, but it might be worth doing for robustness.


  parent reply	other threads:[~2013-05-02 23:04 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-25 19:46 [Bug libgcj/57074] New: " rsa at us dot ibm.com
2013-04-30 20:45 ` [Bug libgcj/57074] " dje at gcc dot gnu.org
2013-05-02  8:18 ` amodra at gmail dot com
2013-05-02  8:54 ` amodra at gmail dot com
2013-05-02 11:35 ` amodra at gmail dot com
2013-05-02 14:02 ` amodra at gmail dot com
2013-05-02 14:25 ` schwab@linux-m68k.org
2013-05-02 15:17 ` jakub at gcc dot gnu.org
2013-05-02 18:21 ` jakub at gcc dot gnu.org
2013-05-02 23:04 ` amodra at gmail dot com [this message]
2013-05-03 10:42 ` amodra at gmail dot com
2013-05-03 15:05 ` jakub at gcc dot gnu.org
2013-05-04  1:21 ` amodra at gmail dot com
2013-05-06 15:21 ` [Bug libgcj/57074] [4.8/4.9 Regression] " jakub at gcc dot gnu.org

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-57074-8172-gOp5kuKA0s@http.gcc.gnu.org/bugzilla/ \
    --to=gcc-bugzilla@gcc.gnu.org \
    --cc=java-prs@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).