This is the mail archive of the
gcc-patches@gcc.gnu.org
mailing list for the GCC project.
Re: RFC: Using DECL_NO_LIMIT_STACK as a backend specific flag
On Wed, Oct 3, 2012 at 5:20 PM, nick clifton <nickc@redhat.com> wrote:
> Hi Ian,
>
>
>> Can't you just keep a list of the decls for which you have issued the
>> warning?
>
>
> Yes - that would work too. In fact I agree that this would be cleaner
> solution in my particular case. I'll create a new patch...
>
>
>
>> How many decls do you expect to be on that list?
>
>
> Not very many. Maybe two or three at most.
>
> But I am interested to know if there is a way for targets to add their own
> information to function decls (and decls in general). If not for this
> particular case, then for problems to come in the future.
To the decl not. But I suppose you are only looking at defined functions,
so it should suffice to amend struct function. It's reasonable to allow
the target to associate extra info with struct function and we already
have a way to do that via the init_machine_status target hook.
Richard.
> Cheers
> Nick
>
>