public inbox for java-prs@sourceware.org
help / color / mirror / Atom feed
From: "egallager at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug classpath/29304] autoconf should be used in libjava to check for fabs, fabsf and scalbn
Date: Wed, 02 Jan 2019 21:43:00 -0000 [thread overview]
Message-ID: <bug-29304-8172-XD1RRvHpyt@http.gcc.gnu.org/bugzilla/> (raw)
In-Reply-To: <bug-29304-8172@http.gcc.gnu.org/bugzilla/>
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29304
--- Comment #4 from Eric Gallager <egallager at gcc dot gnu.org> ---
(In reply to Andrew John Hughes from comment #3)
> No, this is a Classpath bug. Nothing to do with GCJ.
Does it make sense for Classpath and GCC to continue to share a bugzilla these
days? This is far from the only time I've been confused by it... would it be
possible to split them into 2 separate bug databases?
>From java-prs-return-12233-listarch-java-prs=gcc.gnu.org@gcc.gnu.org Wed Jan 02 21:48:55 2019
Return-Path: <java-prs-return-12233-listarch-java-prs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-java-prs@gcc.gnu.org
Received: (qmail 47297 invoked by alias); 2 Jan 2019 21:48:55 -0000
Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <java-prs.gcc.gnu.org>
List-Subscribe: <mailto:java-prs-subscribe@gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/java-prs/>
List-Post: <mailto:java-prs@gcc.gnu.org>
List-Help: <mailto:java-prs-help@gcc.gnu.org>, <http://gcc.gnu.org/ml/#faqs>
Sender: java-prs-owner@gcc.gnu.org
Delivered-To: mailing list java-prs@gcc.gnu.org
Received: (qmail 47245 invoked by uid 48); 2 Jan 2019 21:48:54 -0000
From: "pinskia at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug classpath/29304] autoconf should be used in libjava to check
for fabs, fabsf and scalbn
Date: Wed, 02 Jan 2019 21:48:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: classpath
X-Bugzilla-Component: classpath
X-Bugzilla-Version: 0.15
X-Bugzilla-Keywords:
X-Bugzilla-Severity: normal
X-Bugzilla-Who: pinskia at gcc dot gnu.org
X-Bugzilla-Status: UNCONFIRMED
X-Bugzilla-Resolution:
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-29304-8172-nVLJRmpLVF@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-29304-8172@http.gcc.gnu.org/bugzilla/>
References: <bug-29304-8172@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-q1/txt/msg00001.txt.bz2
Content-length: 835
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=29304
--- Comment #5 from Andrew Pinski <pinskia at gcc dot gnu.org> ---
(In reply to Eric Gallager from comment #4)
> (In reply to Andrew John Hughes from comment #3)
> > No, this is a Classpath bug. Nothing to do with GCJ.
>
> Does it make sense for Classpath and GCC to continue to share a bugzilla
> these days? This is far from the only time I've been confused by it... would
> it be possible to split them into 2 separate bug databases?
I am less confused by the sharing because I know the history (I was one of the
folks who prompted the sharing). I don't think it hurts having the classpath
in GCC's bugzilla and I normally monitor classpath's bug list for accidental
usage there (there was one today but it only happens once every two months so
it is low traffic).
>From java-prs-return-12234-listarch-java-prs=gcc.gnu.org@gcc.gnu.org Fri Dec 20 22:46:29 2019
Return-Path: <java-prs-return-12234-listarch-java-prs=gcc.gnu.org@gcc.gnu.org>
Delivered-To: listarch-java-prs@gcc.gnu.org
Received: (qmail 69829 invoked by alias); 20 Dec 2019 22:46:28 -0000
Mailing-List: contact java-prs-help@gcc.gnu.org; run by ezmlm
Precedence: bulk
List-Id: <java-prs.gcc.gnu.org>
List-Subscribe: <mailto:java-prs-subscribe@gcc.gnu.org>
List-Archive: <http://gcc.gnu.org/ml/java-prs/>
List-Post: <mailto:java-prs@gcc.gnu.org>
List-Help: <mailto:java-prs-help@gcc.gnu.org>, <http://gcc.gnu.org/ml/#faqs>
Sender: java-prs-owner@gcc.gnu.org
Delivered-To: mailing list java-prs@gcc.gnu.org
Received: (qmail 69807 invoked by uid 48); 20 Dec 2019 22:46:28 -0000
From: "redi at gcc dot gnu.org" <gcc-bugzilla@gcc.gnu.org>
To: java-prs@gcc.gnu.org
Subject: [Bug java/64044] Java emits bogus .class$ decls
Date: Fri, 20 Dec 2019 22:46:00 -0000
X-Bugzilla-Reason: CC
X-Bugzilla-Type: changed
X-Bugzilla-Watch-Reason: None
X-Bugzilla-Product: gcc
X-Bugzilla-Component: java
X-Bugzilla-Version: 5.0
X-Bugzilla-Keywords: wrong-code
X-Bugzilla-Severity: normal
X-Bugzilla-Who: redi at gcc dot gnu.org
X-Bugzilla-Status: RESOLVED
X-Bugzilla-Resolution: FIXED
X-Bugzilla-Priority: P3
X-Bugzilla-Assigned-To: unassigned at gcc dot gnu.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags:
X-Bugzilla-Changed-Fields:
Message-ID: <bug-64044-8172-3TbbqU8odA@http.gcc.gnu.org/bugzilla/>
In-Reply-To: <bug-64044-8172@http.gcc.gnu.org/bugzilla/>
References: <bug-64044-8172@http.gcc.gnu.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
X-Bugzilla-URL: http://gcc.gnu.org/bugzilla/
Auto-Submitted: auto-generated
MIME-Version: 1.0
X-SW-Source: 2019-q4/txt/msg00000.txt.bz2
Content-length: 137
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=64044
--- Comment #7 from Jonathan Wakely <redi at gcc dot gnu.org> ---
Fixed by r218018
next parent reply other threads:[~2019-01-02 21:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-29304-8172@http.gcc.gnu.org/bugzilla/>
2019-01-02 21:43 ` egallager at gcc dot gnu.org [this message]
2006-10-01 3:51 [Bug java/29304] New: " howarth at nitro dot med dot uc dot edu
2006-10-01 4:17 ` [Bug classpath/29304] " howarth at nitro dot med dot uc dot edu
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-29304-8172-XD1RRvHpyt@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).