From: Andi Shyti <andi.shyti@intel.com>
To: Chris Wilson <chris@chris-wilson.co.uk>
Cc: igt-dev@lists.freedesktop.org, tvrtko.ursulin@intel.com
Subject: Re: [igt-dev] [PATCH i-g-t] RFC: gem: fix compiler warnings
Date: Mon, 14 Oct 2019 16:16:48 +0300 [thread overview]
Message-ID: <20191014131648.GA5173@intel.intel> (raw)
In-Reply-To: <157105668250.18859.18212130238010224888@skylake-alporthouse-com>
Hi,
> > diff --git a/lib/igt_gt.h b/lib/igt_gt.h
> > index 73b5002..dcaf969 100644
> > --- a/lib/igt_gt.h
> > +++ b/lib/igt_gt.h
> > @@ -75,16 +75,16 @@ extern const struct intel_execution_engine {
> > #define for_if(expr__) if (!(expr__)) {} else
> >
> > #define for_each_engine(fd__, flags__) \
> > - for (const struct intel_execution_engine *e__ = intel_execution_engines;\
> > - e__->name; \
> > - e__++) \
> > - for_if (gem_has_ring(fd__, flags__ = e__->exec_id | e__->flags))
> > + for (const struct intel_execution_engine *e__ ## flags__ = intel_execution_engines;\
> > + e__ ## flags__->name; \
> > + e__ ## flags__++) \
> > + for_if (gem_has_ring(fd__, flags__ = e__ ## flags__->exec_id | e__ ## flags__->flags))
> >
> > #define for_each_physical_engine(fd__, flags__) \
> > - for (const struct intel_execution_engine *e__ = intel_execution_engines;\
> > - e__->name; \
> > - e__++) \
> > - for_if (gem_ring_has_physical_engine(fd__, flags__ = e__->exec_id | e__->flags))
> > + for (const struct intel_execution_engine *e__ ## flags__ = intel_execution_engines;\
> > + e__ ## flags__->name; \
> > + e__ ## flags__++) \
> > + for_if (gem_ring_has_physical_engine(fd__, flags__ = e__ ## flags__->exec_id | e__ ## flags__->flags))
>
> The plan had been to pass the iterator name to the macros. That plan got
> lost somewhere along the way.
yes, we forgot to get rid of this part, but before that we need
to do some refactoring of the gem_engine_topology, because many
things can go wrong there.
If CI does not complain, we can, in the meantime, get this in and
mute the warnings, it's not perfect, but works.
Acked-by: Andi Shyti <andi.shyti@intel.com>
Thanks JP,
Andi
_______________________________________________
igt-dev mailing list
igt-dev@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/igt-dev
next prev parent reply other threads:[~2019-10-14 13:16 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 12:09 [igt-dev] [PATCH i-g-t] RFC: Fix gem test related gcc warnings Juha-Pekka Heikkila
2019-10-14 12:09 ` [igt-dev] [PATCH i-g-t] RFC: gem: fix compiler warnings Juha-Pekka Heikkila
2019-10-14 12:38 ` Chris Wilson
2019-10-14 13:16 ` Andi Shyti [this message]
2019-10-14 13:37 ` Tvrtko Ursulin
2019-10-14 14:01 ` Juha-Pekka Heikkilä
2019-10-14 15:16 ` [igt-dev] ✓ Fi.CI.BAT: success for " Patchwork
2019-10-14 22:00 ` [igt-dev] ✓ Fi.CI.IGT: " Patchwork
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=20191014131648.GA5173@intel.intel \
--to=andi.shyti@intel.com \
--cc=chris@chris-wilson.co.uk \
--cc=igt-dev@lists.freedesktop.org \
--cc=tvrtko.ursulin@intel.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