From: Zopolis0 <creatorsmithmdt@gmail.com>
To: gcc-patches@gcc.gnu.org
Subject: Java front-end and library patches.
Date: Fri, 25 Nov 2022 19:37:44 +1100 [thread overview]
Message-ID: <CAEYL+X8Ps4JvNdnRuGru7Po8o9cUW5mJkDP1TAv9zuZM7K4wpg@mail.gmail.com> (raw)
Disclaimer: this does not currently work.
The front-end and library compile successfully, but fail to link at
the very end.
This is due to a regression caused by
1dedc12d186a110854537e1279b4e6c29f2df35a, which I have been unable to
solve.
Nevertheless, I am posting this patch series for two reasons.
Firstly, to get feedback and reviews on the 56 already existing
patches, even though most are just re-adding code or making idiomatic
changes, so that when the final issue is solved everything has already
been approved (hopefully) and the merge is good to go.
Secondly, to get assistance with the final issue, because it is simply
beyond me, and history has shown that asking for help via gcc-patches
will yield nothing.
You'll need libtool 2.4.7 and a bleeding-edge version of bdwgc to
build it, in case anyone planned to do some testing.
I have compressed the larger patches with bzip3, and attached the
rest, hopefully as plaintext.
next reply other threads:[~2022-11-25 8:37 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-25 8:37 Zopolis0 [this message]
2022-11-28 22:35 ` Joseph Myers
2022-11-30 12:18 ` Zopolis0
2022-11-30 12:50 ` Xi Ruoyao
2022-11-30 18:22 ` Joseph Myers
2022-12-01 11:50 ` Thomas Schwinge
2022-12-02 0:24 ` Zopolis0
2022-12-02 0:26 ` Zopolis0
2022-12-06 11:24 ` Zopolis0
2022-12-12 0:08 ` Zopolis0
2022-12-14 23:01 ` Zopolis0
2022-12-15 2:22 ` Zopolis0
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=CAEYL+X8Ps4JvNdnRuGru7Po8o9cUW5mJkDP1TAv9zuZM7K4wpg@mail.gmail.com \
--to=creatorsmithmdt@gmail.com \
--cc=gcc-patches@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).