Hi,
I found out some small bugs when function is imported from DLL
Test library:
#include
__declspec(dllexport)
bool test() {
return true;
}
extern "C"
BOOL WINAPI DllMain(HINSTANCE hinstDLL, DWORD fdwReason, L
Mikael Pettersson writes:
> I have a toy backend based on the moxie backend as a template. During its
> development I found some oddities in the moxie backend that may be bugs.
>
> 1. The REGNO_OK_FOR_INDEX_P(NUM) macro in moxie.h is:
>
> #define REGNO_OK_FOR_INDEX_P(NUM) MOXIE_FP
>
> Since MOXI
On Thu, 2017-01-12 at 21:49 +, Yuri Gribov wrote:
> Note that documentation for -static-libgcc explicitly mentions that
> There are several situations in which an application should
> use the shared libgcc instead of the static version. The most
> common of these is when
Hi Vladimir,
I'm working on PR target/78660 which is looking like a latent LRA bug.
https://gcc.gnu.org/bugzilla/show_bug.cgi?id=78660
I believe the problem is in the same area as a bug was fixed in 2015:
https://gcc.gnu.org/ml/gcc-patches/2015-01/msg02165.html
Eric pointed out that the new is
On Sun, Jan 15, 2017 at 4:15 PM, Andrew Pinski wrote:
> On Sun, Jan 15, 2017 at 4:09 PM, kugan
> wrote:
>>
>>
>> On 15/01/17 15:57, Andrew Pinski wrote:
>>>
>>> Just this is just an FYI until I reduce the testcases but 5 benchmarks
>>> in SPEC CPU 2006 with fortran code is causing an ICE on
>>> a
I've run into this failure during make check in the past with
a very large make -j value (such as -j128), but today I've had
two consecutive make check runs fail with -j12 and -j8 on my 8
core laptop with no much else going on. The last thing running
was the go test suite. Has something changed
On Mon, Jan 16, 2017 at 4:37 PM, Martin Sebor wrote:
> I've run into this failure during make check in the past with
> a very large make -j value (such as -j128), but today I've had
> two consecutive make check runs fail with -j12 and -j8 on my 8
> core laptop with no much else going on. The last
