__builtin_memcpy() works fine there without any ICE.
```
E:\Desktop>cat test.cpp
auto p = &__builtin_memcpy;
E:\Desktop>gcc test.cpp -c
E:\Desktop>
```
--
Best regards,
lh_mouse
2016-07-05
---
Why do you send messages like these to the various mingw and gcc mailing
lists? There's no context at all, no explanation of what's in your head.
It's like you are only putting a fraction of your thoughts in these emails,
expecting the community to figure out what you mean. When people don't,
then
What happens if you use the built in version?
On Jul 2, 2016 10:19 AM, "lh mouse" wrote:
> Have you guys got g++ 6.1? I am now suffering from an ICE, but
> I am not sure whether it is a bug of GCC. I am looking forward to
> your opinions. If this is indeed a GCC bug I will file it soon.
>
> ** No
mity 2016-07-04 12:43:
> Hello,
Hi,
> for years, I've used mingw-builds ([1], [2]) happily as a default gcc
> toolchain of my choice
> on Windows hosts. However I can see there are no new builds for many
> months although
> there were some gcc releases (6.1, 5.4) in the mean time. That makes
> me
Hello,
for years, I've used mingw-builds ([1], [2]) happily as a default gcc toolchain
of my choice
on Windows hosts. However I can see there are no new builds for many months
although
there were some gcc releases (6.1, 5.4) in the mean time. That makes me
wondering about
its current status.
