>
> Not sure if this is a good idea, since this means the CRT built by clang
> cannot be used by gcc. Maybe modify it to be emitted as clang-crt1.o?
> (Along with changing clang to prefer clang-crt1.o if it exists).
Well ideally I would be looking at a way to get this asm section to compile
under
On 8/5/2015 04:59, Martell Malone wrote:
> Hi
>
> I currently apply this to clang when building mingw-w64-crt for x64 when
> building with clang.
> This is not exactly a blocker for me because my focus is x86 and arm but
> maybe someone has a better work around.
>
> jon_y?
>
> Thoughts
>
Not s
Hi
I currently apply this to clang when building mingw-w64-crt for x64 when
building with clang.
This is not exactly a blocker for me because my focus is x86 and arm but
maybe someone has a better work around.
jon_y?
Thoughts
>From 38ff74f5679980d7a251049b53554404d46006bb Mon Sep 17 00:00:00 20
On 9/29/2012 03:30, Kai Tietz wrote:
> 2012/9/28 Earnie Boyd :
>> Please forgive my laziness as not having enough time yet to download
>> and format an environment with 4.8 GCC as yet. Is there a predefined
>> macro to indicate when I have SEH support?
>
> Yes, there is.
>
__SEH__
signatur
2012/9/28 Earnie Boyd :
> Please forgive my laziness as not having enough time yet to download
> and format an environment with 4.8 GCC as yet. Is there a predefined
> macro to indicate when I have SEH support?
Yes, there is.
Regards,
Kai
Please forgive my laziness as not having enough time yet to download
and format an environment with 4.8 GCC as yet. Is there a predefined
macro to indicate when I have SEH support?
--
Earnie
-- https://sites.google.com/site/earnieboyd
2012/8/6 NightStrike:
> On Sun, Aug 5, 2012 at 1:09 PM, JonY wrote:
>> Actually, I just succeeded in getting around that error,
>> x86_64-w64-mingw32-gcc 4.8.0 is working fine here.
>>
>> Remove the --enable-sjlj-exceptions part from your configure, don't
>> disable it either. --enable-sjlj-excepti
2012/8/4 Kai Tietz:
> After crt was built and installed, use 'make
> all-target-libgcc' and then use 'make install-target-libgcc'.
The same error.
--
Regards,
niXman
___
Dual-target(32 & 64 bit) MinGW compilers for 32 and 64 bit Windows:
http://s
2012/8/8 niXman
> 2012/8/8 Ruben Van Boxem:
> > That's not what was implemented. What was implemented is the
> > native (MSVC compatible?) Win64 native exception handling.
> Why Win64? SEH that, only for Win64 is implemented/works?
>
> P.S.
> Probably my questions seem silly, but I never worked fo
2012/8/8 Ruben Van Boxem:
> That's not what was implemented. What was implemented is the
> native (MSVC compatible?) Win64 native exception handling.
Why Win64? SEH that, only for Win64 is implemented/works?
P.S.
Probably my questions seem silly, but I never worked for windows.
Some years I work a
2012/8/8 niXman
> I got to build only for x86_64 target. For the i686 - I did not.
> I have tested this example:
> try {
>int* i = 0;
>cout << *i << endl;
> } catch ( ... ) {
>cout << "exception" << endl;
> }
>
> the exception is not caught.
>
That's not what was implemented. What wa
I got to build only for x86_64 target. For the i686 - I did not.
I have tested this example:
try {
int* i = 0;
cout << *i << endl;
} catch ( ... ) {
cout << "exception" << endl;
}
the exception is not caught.
I have two questions:
1) What kind of SEH was added for WIN platform? How does
On Mon, Aug 6, 2012 at 11:22 AM, Ruben Van Boxem
wrote:
> Op 6 aug. 2012 23:20 schreef "JonY" het
> volgende:
>> > What libgcc was built? dw2 or sjlj (or something else)?
>> 64bit libgcc_s_seh-1.dll, 32bit libgcc_s_sjlj-1.dll.
> Looking good then :-)
Yeah, this is actually a really awesome thing
Op 6 aug. 2012 23:20 schreef "JonY" het
volgende:
>
> On 8/7/2012 05:01, Ruben Van Boxem wrote:
> > Op 6 aug. 2012 22:59 schreef "JonY" het
> > volgende:
> >>
> >> On 8/7/2012 02:01, niXman wrote:
> >>> 2012/8/6 JonY:
> Actually, I just succeeded in getting around that error,
> x86_64-w
On 8/7/2012 05:03, niXman wrote:
> 2012/8/7 JonY:
>
>> You can leave the --enable-sjlj-exceptions for the 32bit case for now,
>> since it can't do SEH anyway.
>
> libgcc/unwind-c.c: In function '__gcc_personality_seh0':
> libgcc/unwind-c.c:242:14: error: '__gcc_personality_imp' undeclared
>
>
On 8/7/2012 05:01, Ruben Van Boxem wrote:
> Op 6 aug. 2012 22:59 schreef "JonY" het
> volgende:
>>
>> On 8/7/2012 02:01, niXman wrote:
>>> 2012/8/6 JonY:
Actually, I just succeeded in getting around that error,
x86_64-w64-mingw32-gcc 4.8.0 is working fine here.
Remove the --ena
2012/8/7 JonY:
> You can leave the --enable-sjlj-exceptions for the 32bit case for now,
> since it can't do SEH anyway.
libgcc/unwind-c.c: In function '__gcc_personality_seh0':
libgcc/unwind-c.c:242:14: error: '__gcc_personality_imp' undeclared
--
Regards,
niXman
__
Op 6 aug. 2012 22:59 schreef "JonY" het
volgende:
>
> On 8/7/2012 02:01, niXman wrote:
> > 2012/8/6 JonY:
> >> Actually, I just succeeded in getting around that error,
> >> x86_64-w64-mingw32-gcc 4.8.0 is working fine here.
> >>
> >> Remove the --enable-sjlj-exceptions part from your configure, do
On 8/7/2012 02:01, niXman wrote:
> 2012/8/6 JonY:
>> Actually, I just succeeded in getting around that error,
>> x86_64-w64-mingw32-gcc 4.8.0 is working fine here.
>>
>> Remove the --enable-sjlj-exceptions part from your configure, don't
>> disable it either. --enable-sjlj-exceptions still makes wi
2012/8/6 JonY:
> Actually, I just succeeded in getting around that error,
> x86_64-w64-mingw32-gcc 4.8.0 is working fine here.
>
> Remove the --enable-sjlj-exceptions part from your configure, don't
> disable it either. --enable-sjlj-exceptions still makes win64 target use
> sjlj, though there is a
On Sun, Aug 5, 2012 at 1:09 PM, JonY wrote:
> On 8/5/2012 16:59, niXman wrote:
>> 2012/8/5 Ruben Van Boxem:
>>
>>> This might be it. I build and install libgcc before the rest of gcc. I added
>>> this step to resolve some link error I encountered once, and left it in to
>>> be sure it never happen
On 8/5/2012 16:59, niXman wrote:
> 2012/8/5 Ruben Van Boxem:
>
>> This might be it. I build and install libgcc before the rest of gcc. I added
>> this step to resolve some link error I encountered once, and left it in to
>> be sure it never happened again.
>
> In other words, it turns out that th
2012/8/5 Ruben Van Boxem:
> This might be it. I build and install libgcc before the rest of gcc. I added
> this step to resolve some link error I encountered once, and left it in to
> be sure it never happened again.
In other words, it turns out that there were made some changes in
trunk that n
Op 5 aug. 2012 08:47 schreef "niXman" het volgende:
>
> 2012/8/4 Kai Tietz:
> > Hmm, I guess you have already installed a prior version of compiler to
> > same sysroot. Am I right?
> No.
>
>
> > Nevertheless I could solve the issue by
> > the following steps. After crt was built and installed, u
2012/8/4 Kai Tietz:
> Hmm, I guess you have already installed a prior version of compiler to
> same sysroot. Am I right?
No.
> Nevertheless I could solve the issue by
> the following steps. After crt was built and installed, use 'make
> all-target-libgcc' and then use 'make install-target-libg
2012/8/4 niXman :
> 2012/8/4 Ruben Van Boxem:
>> I do not see this failure.
>
> The same error:
> gcc-trunk/libgcc/unwind-c.c: In function '__gcc_personality_seh0':
> gcc-trunk/libgcc/unwind-c.c:242:14: error: '__gcc_personality_imp'
> undeclared (first use in this function)
>
>
>
> --
> Regards,
>
2012/8/4 Ruben Van Boxem:
> I do not see this failure.
The same error:
gcc-trunk/libgcc/unwind-c.c: In function '__gcc_personality_seh0':
gcc-trunk/libgcc/unwind-c.c:242:14: error: '__gcc_personality_imp'
undeclared (first use in this function)
--
Regards,
niXman
__
2012/8/4 niXman
> 2012/8/4 Ruben Van Boxem:
>
> > I am building GCC and verifying as you are reading this email :P
>
> http://gcc.gnu.org/ml/gcc-help/2012-08/msg00018.html
>
I do not see this failure. I have a working GCC 4.8 toolchain with SEH C++
exceptions (which work, btw!). This is with cur
2012/8/4 Ruben Van Boxem:
> I am building GCC and verifying as you are reading this email :P
http://gcc.gnu.org/ml/gcc-help/2012-08/msg00018.html
--
Regards,
niXman
___
Dual-target(32 & 64 bit) MinGW compilers for 32 and 64 bit Windows:
http://so
2012/7/27 niXman
> 2012/7/27 NightStrike:
> >
> > You might want to check out gcc 4.7.2 with current trunk mingw-w64
> > crt/headers. I believe SEH is in as of the 4th of July.
>
> Are you saying that this code will be execute correctly?
>
> try {
>int* i = 0;
>cout << *i << endl;
> } ca
On Jul 27, 2012, at 9:10 AM, niXman wrote:
> 2012/7/27 NightStrike:
>>
>> You might want to check out gcc 4.7.2 with current trunk mingw-w64
>> crt/headers. I believe SEH is in as of the 4th of July.
>
> Are you saying that this code will be execute correctly?
>
> try {
> int* i = 0;
> co
2012/7/27 NightStrike:
>
> You might want to check out gcc 4.7.2 with current trunk mingw-w64
> crt/headers. I believe SEH is in as of the 4th of July.
Are you saying that this code will be execute correctly?
try {
int* i = 0;
cout << *i << endl;
} catch ( ... ) {
cout << "exception" <<
On Tue, Sep 27, 2011 at 7:27 PM, niXman wrote:
> 2011/9/26 xunxun
>> On 2011/9/26 3:15, niXman wrote:
>>
>> All greetings!
>> Tell me please, is there any information about the plans on implementation
>> SEH of exceptions? Where it is possible to learn about the plans on its
>> implementation?
>>
I know this library. I wanted to know whether the GCC developers do have any
plans on the SEH implementation.
I understand that MinGW-w64 project is not developed by GCC. But it seems
like Kai is involved in the development of GCC.
Thanks.
niXman.
2011/9/26 xunxun
> On 2011/9/26 3:15, niXma
On 2011/9/26 3:15, niXman wrote:
All greetings!
Tell me please, is there any information about the plans on
implementation SEH of exceptions? Where it is possible to learn about
the plans on its implementation?
Thanks!
niXman.
I don't know.
At present you can see :
http://www.programmingu
All greetings!
Tell me please, is there any information about the plans on implementation
SEH of exceptions? Where it is possible to learn about the plans on its
implementation?
Thanks!
niXman.
--
All of the data generat
Hello everybody,
This simple MSVC application is loading a MinGW dll and calling a
function which raises an exception.
The 32-bit version of application is catching the exception as expected,
but 64-bit version of application is crashing.
So far my research of the problem goes with no success.
37 matches
Mail list logo
