Hi all,
>>> if (a == b)
>>> ...
>>>
>>> # c = PHI
>>>
>>> where we'd lose eliding such a conditional. IMHO that's bad
>>> and very undesirable.
>> But if we only suppress this optimization for pointers is it that terrible?
>
> I've at least seen a lot of cases with c = PHI for null pointer
>
Hi Hongtao,
I have left Intel 3 years ago. If you have any questions regarding MIC
offloading, you can reach me by iver...@gmail.com
Hongtao Liu :
> I don't konw this guy ilya.ver...@intel.com.
> Do you know him/her, H.J?
>
> --
> BR,
> Hongtao
|| Ilya
On Wed, 8 May 2019, Tejas Joshi wrote:
> Hello.
> I can't figure out from the documentation how to add test cases in the
> testsuite and inspect the results. How can I do that? Although, Taking
> the mentioned conditions under consideration, I have made another
> patch, attached.
This patch still
On Wed, 8 May 2019, Tejas Joshi wrote:
> Is this the way test cases should be added and checked?
Yes, that's appropriate for tests of roundeven optimization for constant
arguments.
When you get onto testing roundevenf128 (to cover various cases with
113-bit precision), you'll need to make thos
Snapshot gcc-7-20190509 is now available on
ftp://gcc.gnu.org/pub/gcc/snapshots/7-20190509/
and on various mirrors, see http://gcc.gnu.org/mirrors.html for details.
This snapshot has been generated from the GCC 7 SVN branch
with the following options: svn://gcc.gnu.org/svn/gcc/branches/gcc-7
