public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* Targetting p0847 for GCC14 (explicit object parameter)
@ 2023-06-08  4:06 waffl3x
  2023-06-08  7:52 ` Jonathan Wakely
  2023-06-08 14:12 ` Ben Boeckel
  0 siblings, 2 replies; 4+ messages in thread
From: waffl3x @ 2023-06-08  4:06 UTC (permalink / raw)
  To: gcc

I would like to boldly suggest implementing P0847 should be targeted at
GCC14. In my anecdotal experiences, this feature is very important to
people, and very important to myself, I believe it should be a priority.

I am not suggesting this without offering to contribute, however
because of my inexperience with compiler hacking I am concerned I would
hinder efforts. With that said, if no one is interested in starting
work on it, but there is consensus that the feature is important
enough, then I will do my best to take up that job.

If this was already the understood plan for GCC14, I apologize for my
ignorance on the matter. I searched around and couldn't find any
information regarding it, the mail list didn't seem to have any results
either. If it's there and I missed it, please do point it out. I am
also wondering if there is a public document with information about the
feature roadmap? I can understand why there isn't one if that isn't the
case, I imagine it would just cause a nuisance for the developers. I
had read the GCC Development Plan document a few months ago and given
the information in it I decided to wait for development to move on to
GCC14 before getting in touch. In hindsight that might have been a
mistake, oops!

I apologize if I overlooked something obvious, please don't hesitate to
correct any misconceptions I'm having here as it's not my intention to
step on any toes here, I just really really value this feature and want
to see it sooner rather than later.

I look forward to hearing everyone's input,
    -Alex

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Targetting p0847 for GCC14 (explicit object parameter)
  2023-06-08  4:06 Targetting p0847 for GCC14 (explicit object parameter) waffl3x
@ 2023-06-08  7:52 ` Jonathan Wakely
  2023-06-08 14:22   ` Jason Merrill
  2023-06-08 14:12 ` Ben Boeckel
  1 sibling, 1 reply; 4+ messages in thread
From: Jonathan Wakely @ 2023-06-08  7:52 UTC (permalink / raw)
  To: waffl3x; +Cc: gcc

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

On Thu, 8 Jun 2023, 05:07 waffl3x via Gcc, <gcc@gcc.gnu.org> wrote:

> I would like to boldly suggest implementing P0847 should be targeted at
> GCC14. In my anecdotal experiences, this feature is very important to
> people, and very important to myself, I believe it should be a priority.
>
> I am not suggesting this without offering to contribute, however
> because of my inexperience with compiler hacking I am concerned I would
> hinder efforts. With that said, if no one is interested in starting
> work on it, but there is consensus that the feature is important
> enough, then I will do my best to take up that job.
>
> If this was already the understood plan for GCC14, I apologize for my
> ignorance on the matter. I searched around and couldn't find any
> information regarding it, the mail list didn't seem to have any results
> either. If it's there and I missed it, please do point it out. I am
> also wondering if there is a public document with information about the
> feature roadmap?


No, we don't do that. It doesn't really make sense for a project like gcc.
There is no management setting goals and priorities, nor assigning work to
anybody.

For large-ish features like this there should be a bugzilla ticket. If
somebody is planning to work on it, that ticket will be ASSIGNED to them.
Any plans that exist will probably be noted there.


I can understand why there isn't one if that isn't the
> case, I imagine it would just cause a nuisance for the developers. I
> had read the GCC Development Plan document a few months ago and given
> the information in it I decided to wait for development to move on to
> GCC14 before getting in touch. In hindsight that might have been a
> mistake, oops!
>
> I apologize if I overlooked something obvious, please don't hesitate to
> correct any misconceptions I'm having here as it's not my intention to
> step on any toes here, I just really really value this feature and want
> to see it sooner rather than later.
>
> I look forward to hearing everyone's input,
>     -Alex
>

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Targetting p0847 for GCC14 (explicit object parameter)
  2023-06-08  4:06 Targetting p0847 for GCC14 (explicit object parameter) waffl3x
  2023-06-08  7:52 ` Jonathan Wakely
@ 2023-06-08 14:12 ` Ben Boeckel
  1 sibling, 0 replies; 4+ messages in thread
From: Ben Boeckel @ 2023-06-08 14:12 UTC (permalink / raw)
  To: waffl3x; +Cc: gcc

On Thu, Jun 08, 2023 at 04:06:24 +0000, waffl3x via Gcc wrote:
> I would like to boldly suggest implementing P0847 should be targeted at
> GCC14. In my anecdotal experiences, this feature is very important to
> people, and very important to myself, I believe it should be a priority.
> 
> I am not suggesting this without offering to contribute, however
> because of my inexperience with compiler hacking I am concerned I would
> hinder efforts. With that said, if no one is interested in starting
> work on it, but there is consensus that the feature is important
> enough, then I will do my best to take up that job.

Note that one way to help with a "feature that is very important" to
oneself without compiler experience is to help write test cases (even
better if it includes the necessary `dejagnu` markup). Corner cases are
typically the trickiest to handle and filling it out ahead of time is
likely very helpful to whoever does end up working on it. Indeed,
because you're (likely) different from the feature implementer, you can
help fill in blind spots that may be missed otherwise.

It would also be useful to be somewhat systematic about it as well and
take notes on what, specifically, is being tested in each case as well
as where known gaps in the test cases exist.

--Ben

^ permalink raw reply	[flat|nested] 4+ messages in thread

* Re: Targetting p0847 for GCC14 (explicit object parameter)
  2023-06-08  7:52 ` Jonathan Wakely
@ 2023-06-08 14:22   ` Jason Merrill
  0 siblings, 0 replies; 4+ messages in thread
From: Jason Merrill @ 2023-06-08 14:22 UTC (permalink / raw)
  To: Jonathan Wakely; +Cc: waffl3x, gcc

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

On Thu, Jun 8, 2023 at 3:54 AM Jonathan Wakely via Gcc <gcc@gcc.gnu.org>
wrote:

> On Thu, 8 Jun 2023, 05:07 waffl3x via Gcc, <gcc@gcc.gnu.org> wrote:
>
> > I would like to boldly suggest implementing P0847 should be targeted at
> > GCC14. In my anecdotal experiences, this feature is very important to
> > people, and very important to myself, I believe it should be a priority.
> >
> > I am not suggesting this without offering to contribute, however
> > because of my inexperience with compiler hacking I am concerned I would
> > hinder efforts. With that said, if no one is interested in starting
> > work on it, but there is consensus that the feature is important
> > enough, then I will do my best to take up that job.
> >
> > If this was already the understood plan for GCC14, I apologize for my
> > ignorance on the matter. I searched around and couldn't find any
> > information regarding it, the mail list didn't seem to have any results
> > either. If it's there and I missed it, please do point it out. I am
> > also wondering if there is a public document with information about the
> > feature roadmap?
>
> No, we don't do that. It doesn't really make sense for a project like gcc.
> There is no management setting goals and priorities, nor assigning work to
> anybody.
>
> For large-ish features like this there should be a bugzilla ticket. If
> somebody is planning to work on it, that ticket will be ASSIGNED to them.
> Any plans that exist will probably be noted there.
>

Specifically: https://gcc.gnu.org/bugzilla/show_bug.cgi?id=102609

In general the implementation status of new language features can be found
at https://gcc.gnu.org/projects/cxx-status.html ; for features not yet
implemented, the "No" links to the corresponding PR.

I definitely agree that we want the feature, but I don't expect to have
time to implement it myself for GCC 14.  If you're interested in looking at
it, that's great!  Please feel free to contact me with any questions.

Jason

^ permalink raw reply	[flat|nested] 4+ messages in thread

end of thread, other threads:[~2023-06-08 14:22 UTC | newest]

Thread overview: 4+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2023-06-08  4:06 Targetting p0847 for GCC14 (explicit object parameter) waffl3x
2023-06-08  7:52 ` Jonathan Wakely
2023-06-08 14:22   ` Jason Merrill
2023-06-08 14:12 ` Ben Boeckel

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).