Objet : Developers list for StarPU
Archives de la liste
- From: Samuel Thibault <samuel.thibault@ens-lyon.org>
- To: George Russell <george@codeplay.com>, "starpu-devel@lists.gforge.inria.fr" <starpu-devel@lists.gforge.inria.fr>
- Subject: Re: [Starpu-devel] Suppressing MSVC warnings on StarPU macros
- Date: Wed, 27 Apr 2011 17:48:04 +0200
- List-archive: <http://lists.gforge.inria.fr/pipermail/starpu-devel>
- List-id: "Developers list. For discussion of new features, code changes, etc." <starpu-devel.lists.gforge.inria.fr>
Samuel Thibault, le Wed 20 Apr 2011 15:56:00 +0200, a écrit :
> George Russell, le Wed 20 Apr 2011 15:37:44 +0200, a écrit :
> > These are those using the do { ... } while (0) technique for multi-line
> > macros.
> >
> > Rewriting the loop as do { ... } while (0,false) suppresses the warning,
> > without adverse effect on the correctness.
>
> Well, as the thread itself says about __LINE__==-1, such techniques tend
> to get the warning again with some new release of the compiler.
>
> Actually I'd say we should rather just turn them into inlines. And
> concerning the REPORT_ERROR macros with the switch() {} statement, it
> should probably rather be a starpu function.
I have done so.
Samuel
- [Starpu-devel] Suppressing MSVC warnings on StarPU macros, George Russell, 20/04/2011
- <Suite(s) possible(s)>
- Re: [Starpu-devel] Suppressing MSVC warnings on StarPU macros, Samuel Thibault, 20/04/2011
- Re: [Starpu-devel] Suppressing MSVC warnings on StarPU macros, Samuel Thibault, 27/04/2011
Archives gérées par MHonArc 2.6.19+.