On Thu, Apr 27, 2017 at 02:46:23PM +0200, Jakub Jelinek wrote:
> On Thu, Apr 27, 2017 at 01:37:02PM +0100, Richard Earnshaw (lists) wrote:
> > > + if (ncrn & 1)
> > > + {
> > > + int res = arm_needs_doubleword_align (mode, type);
> > > + /* Only warn during RTL expansion of call stmts, otherwise we would
> > > + warn e.g. during gimplification even on functions that will be
> > > + always inlined, and we'd warn multiple times. Don't warn when
> > > + called in expand_function_start either, as we warn instead in
> > > + arm_function_arg_boundary in that case. */
> > > + if (res < 0 && warn_psabi && currently_expanding_gimple_stmt)
> > > + inform (input_location, "parameter passing for argument of type "
> > > + "%qT will change in GCC 7.1", type);
> >
> > Should this be a real warning? The generated code, after all, is
> > potentially non-compliant with the ABI, and it might be nice if werror
> > could be used to catch this.
>
> But it isn't a bug or questionable thing in user's code, but a compiler bug,
> and while in some cases it may be possible to work around it easily, in some
> cases with more effort, in some cases it may be very hard.
Yeah, plus the principle that we shouldn't backport new warnings to release
branches.
Marek
