search for: 77e73887

...at x10sys.com> wrote: > Patch looks good so I committed it. I'd be interested in knowing what > your test results are once you start testing with the Win32 port. I tested Signals.cpp and verified that the CTRL/C handler works, as does the stack trace. In fact, here's a sample: 77E73887 (0xE06D7363 0x00000001 0x00000003 0x0012FF28), RaiseException()+0080 bytes(s) 10226DB9 (0x0012FF44 0x0040DEFC 0x00020024 0x00647373), _CxxThrowException()+0057 bytes(s) 00401822 (0x0012FFC0 0x00409A2C 0x00000001 0x003250D0), XYZ::func()+0034 bytes(s), c:\projects\llvm\test.cpp, line 12 004017ED (0x...

...; Patch looks good so I committed it. I'd be interested in knowing what > > your test results are once you start testing with the Win32 port. > > I tested Signals.cpp and verified that the CTRL/C handler works, as does > the stack trace. In fact, here's a sample: > > 77E73887 (0xE06D7363 0x00000001 0x00000003 0x0012FF28), RaiseException()+0080 bytes(s) > 10226DB9 (0x0012FF44 0x0040DEFC 0x00020024 0x00647373), _CxxThrowException()+0057 bytes(s) > 00401822 (0x0012FFC0 0x00409A2C 0x00000001 0x003250D0), XYZ::func()+0034 bytes(s), c:\projects\llvm\test.cpp, line 12 &g...

...ted it. I'd be interested in knowing what > > > your test results are once you start testing with the Win32 port. > > > > I tested Signals.cpp and verified that the CTRL/C handler works, as does > > the stack trace. In fact, here's a sample: > > > > 77E73887 (0xE06D7363 0x00000001 0x00000003 0x0012FF28), RaiseException()+0080 bytes(s) > > 10226DB9 (0x0012FF44 0x0040DEFC 0x00020024 0x00647373), _CxxThrowException()+0057 bytes(s) > > 00401822 (0x0012FFC0 0x00409A2C 0x00000001 0x003250D0), XYZ::func()+0034 bytes(s), c:\projects\llvm\test.cpp,...

...in knowing what > > > > your test results are once you start testing with the Win32 port. > > > > > > I tested Signals.cpp and verified that the CTRL/C handler works, as does > > > the stack trace. In fact, here's a sample: > > > > > > 77E73887 (0xE06D7363 0x00000001 0x00000003 0x0012FF28), RaiseException()+0080 bytes(s) > > > 10226DB9 (0x0012FF44 0x0040DEFC 0x00020024 0x00647373), _CxxThrowException()+0057 bytes(s) > > > 00401822 (0x0012FFC0 0x00409A2C 0x00000001 0x003250D0), XYZ::func()+0034 bytes(s), c:\projects\llvm\...

Patch looks good so I committed it. I'd be interested in knowing what your test results are once you start testing with the Win32 port. Reid. On Sat, 2004-09-18 at 12:01, Jeff Cohen wrote: > Here's my first take on Path.cpp. It has a few holes still but it ought > to be basically functional. > > A few observations: > > First, the Win32 version still has a lot of code

Here's my first take on Path.cpp. It has a few holes still but it ought to be basically functional. A few observations: First, the Win32 version still has a lot of code in common with Unix. This code should be pulled out into a common file. Second, some of the functions leave me scratching me head. What purpose does create_file serve? Is there really a need to create empty files? (It