public inbox for kawa@sourceware.org
 help / color / mirror / Atom feed
From: Panicz Maciej Godek <godek.maciek@gmail.com>
To: Per Bothner <per@bothner.com>
Cc: kawa@sourceware.org
Subject: Re: Building for Android
Date: Fri, 21 Oct 2022 21:19:13 +0200	[thread overview]
Message-ID: <CAMFYt2bukzei_WEzC85rMGxXHU2kci+KC=tLZNH6Q+rA2D7b5A@mail.gmail.com> (raw)
In-Reply-To: <b0e04712-c37c-175c-2507-f3ed2deadf85@bothner.com>

[-- Attachment #1: Type: text/plain, Size: 1673 bytes --]

pt., 21 paź 2022, 20:12 użytkownik Per Bothner <per@bothner.com> napisał:

>
>
> > While this isn't something I can't live with - because I don't have that
> many such use cases - I wanted to ask about the chances of resolving that
> issue?
>
> Well, if the fix in my previous sets USE_SYMBOLIC to false for you,
> the part of the problem is solved.
>
> If you're still getting invalidly mangled field names, we should figure
> out why.
>

The patch does solve the issue with the interference between --with-android
and --with-java-source (I tested it with version 9 to see whether the d8
tool would stop complaining - but it didn't help, although it didn't break
anything either)

However, the issue with accessing superclass properties with mangled names
from a subclass remains unsolved.

When I run javap on the compiled superclass, it gives the following result
(I'm pasting only the problematic identifiers):

public abstract class CharPainter implements Painter {
              public gnu.math.RealNum shift$Mnleft;
                           public gnu.math.RealNum shift$Mntop;
                                        public gnu.math.RealNum
clip$Mnleft;                                                    public
gnu.math.RealNum clip$Mntop;
     public gnu.math.RealNum clip$Mnwidth;
                 public gnu.math.RealNum clip$Mnheight;
                              public Position marked$Mncursor$Mnposition;
                                           public boolean
selection$Mndrawing$Mnmode$Qu;
...
}

This doesn't look incorrect to me - I'd suspect that the problem might be
on the side of the subclass.

>

  reply	other threads:[~2022-10-21 19:19 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-18 14:57 Panicz Maciej Godek
2022-10-18 15:25 ` Per Bothner
2022-10-18 18:25   ` Panicz Maciej Godek
2022-10-19  9:15     ` Panicz Maciej Godek
2022-10-19 16:05       ` Per Bothner
2022-10-19 17:09         ` Panicz Maciej Godek
2022-10-20  5:35           ` Panicz Maciej Godek
2022-10-20 20:48             ` Panicz Maciej Godek
2022-10-21  5:14               ` Panicz Maciej Godek
2022-10-21 13:59                 ` Panicz Maciej Godek
2022-10-21 18:11                   ` Per Bothner
2022-10-21 19:19                     ` Panicz Maciej Godek [this message]
2022-10-21 19:31                       ` Per Bothner
2022-10-21 19:45                         ` Panicz Maciej Godek
2022-10-21 20:13                           ` Panicz Maciej Godek
2022-10-22  6:26                           ` Per Bothner
2022-10-22  9:31                             ` Panicz Maciej Godek
2022-10-22 12:08                               ` Panicz Maciej Godek
2022-10-24  7:22                                 ` Panicz Maciej Godek
2022-10-24 10:48                                   ` Per Bothner
2022-10-24 12:01                                     ` Panicz Maciej Godek
2022-10-21 18:00           ` Per Bothner

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='CAMFYt2bukzei_WEzC85rMGxXHU2kci+KC=tLZNH6Q+rA2D7b5A@mail.gmail.com' \
    --to=godek.maciek@gmail.com \
    --cc=kawa@sourceware.org \
    --cc=per@bothner.com \
    /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).