From: Matt Rice <ratmice@gmail.com>
To: Tom Tromey <tom@tromey.com>
Cc: Giah de Barag <gdb@crelg.com>, GDB Patches <gdb-patches@sourceware.org>
Subject: Re: Restored Objective-C language support
Date: Thu, 15 Sep 2016 00:31:00 -0000 [thread overview]
Message-ID: <CACTLOFqqr6ab08h1LA8yv5=wOs0YBvK+x_VD93LzNn2BG3ffjA@mail.gmail.com> (raw)
In-Reply-To: <87intyrt26.fsf@tromey.com>
On Wed, Sep 14, 2016 at 3:54 PM, Tom Tromey <tom@tromey.com> wrote:
>>>>>> "Giah" == Giah de Barag <gdb@crelg.com> writes:
>
> Giah> Patches are presented which restore objective-c language support.
> Giah> These patches are relative to the head of the gdb-7.11-branch.
>
> I didn't read the patches really, but I feel a bit responsible since I
> merged objc-exp.y into c-exp.y back in the day, and apparently not well.
>
> I think the most important thing to do to avoid future problems is make
> sure the objc tests are working. The last time I looked at this, I
> think they weren't working properly at all.
I Agree, part of the problem is that during some "modernization" of
the objective-c runtime, the "Object" class, the root class that is
distributed with the runtime was neutered basically into
non-existence...
I didn't really manage to catch it before release, and gave up afterwords...
https://github.com/gnustep/libobjc2/blob/master/objc/Object.h
https://gcc.gnu.org/git/?p=gcc.git;a=blob;f=libobjc/objc/Object.h;h=f69f8139e8c0b0841e806f72747d09ca641dd2f8;hb=refs/heads/trunk
There used to be... methods, in particular there was a method called 'new'
which allowed one to actually allocate and instantiate an object in a
portable fashion.
given that there are about 50 different objective-c runtimes,
It seemed completely out of scope for the gdb testsuite...
I'm not sure what gcc and clang themselves are using to test i'd
imagine the c/runtime specific interface they provide... but it's a
bit inconvenient for a project like gdb that sits between gcc and
something external like gnustep (which provides its own mechanism for
instantiating objects).
> Also, it would be good to have new tests for the patches you wrote.
>
> Giah> Also, this is the first time I am doing something like this, so if
> Giah> I am neglecting any rule of communication of this list, please
> Giah> inform me, and I will correct it.
>
> Nothing wrong with your email but there are some contribution
> instructions for gdb:
>
> https://sourceware.org/gdb/wiki/ContributionChecklist
>
> Tom
next prev parent reply other threads:[~2016-09-15 0:31 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-13 21:21 Giah de Barag
2016-09-14 22:54 ` Tom Tromey
2016-09-15 0:31 ` Matt Rice [this message]
2016-09-15 19:12 ` Giah de Barag
2016-09-16 5:52 ` Giah de Barag
2016-09-27 21:03 ` Giah de Barag
2016-10-12 2:14 ` Tom Tromey
2016-09-14 6:09 Roland Schwingel
2016-09-14 7:25 ` Giah de Barag
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='CACTLOFqqr6ab08h1LA8yv5=wOs0YBvK+x_VD93LzNn2BG3ffjA@mail.gmail.com' \
--to=ratmice@gmail.com \
--cc=gdb-patches@sourceware.org \
--cc=gdb@crelg.com \
--cc=tom@tromey.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