public inbox for gcc@gcc.gnu.org
 help / color / mirror / Atom feed
* GSoC: cp demangle non recursive
@ 2022-03-18 19:38 Krishna Narayanan
  2022-03-22 17:01 ` Martin Jambor
  0 siblings, 1 reply; 2+ messages in thread
From: Krishna Narayanan @ 2022-03-18 19:38 UTC (permalink / raw)
  To: Martin Jambor; +Cc: gcc

Hello,
I have a doubt regarding the recursion part in demangle.c, what should
be the expected report when the recursion limit has been
reached,Secondly the verbose which has to be printed for the C
linkage, what should be the info that has to be displayed.
I have started working on the introduction of stacks in the file but
there is implicit recursion which hinders a lot,Hopefully I should
come up with something comprehensive subsequently.
Thanks,
Krishna Narayanan.

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

* Re: GSoC: cp demangle non recursive
  2022-03-18 19:38 GSoC: cp demangle non recursive Krishna Narayanan
@ 2022-03-22 17:01 ` Martin Jambor
  0 siblings, 0 replies; 2+ messages in thread
From: Martin Jambor @ 2022-03-22 17:01 UTC (permalink / raw)
  To: Krishna Narayanan; +Cc: gcc

Hello,

On Sat, Mar 19 2022, Krishna Narayanan wrote:
> Hello,
> I have a doubt regarding the recursion part in demangle.c, what should
> be the expected report when the recursion limit has been
> reached,

Look at the comment of the d_demangle function.  In the new scheme of
things, the failure would essentially be a memory allocation failure.  

> Secondly the verbose which has to be printed for the C
> linkage, what should be the info that has to be displayed.

I'm not sure I understand, but the demangler should have exactly the
same output as now, only the internal implementation should change.

Good luck,

Martin

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

end of thread, other threads:[~2022-03-22 17:01 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-03-18 19:38 GSoC: cp demangle non recursive Krishna Narayanan
2022-03-22 17:01 ` Martin Jambor

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