First I'd like that add that it's not technically us trying to run this on
vintage PIII :-).
So I was able to resolve the issue by passing the /arch:SSE parameter to
the C/C++ compiler options. Thanks!
On Wednesday, October 5, 2016 at 9:33:06 AM UTC-5, Adam Cozzette wrote:
>
> That's good to kn
First I'd like that add that it's not technically us trying to run this on
vintage PIII :-).
So I was able to resolve the issue by passing the /arch:SSE parameter to
the C/C++ compiler options. Thanks!
On Wednesday, October 5, 2016 at 9:33:06 AM UTC-5, Adam Cozzette wrote:
>
> That's good to kn
First I'd like that add that it's not technically us trying to run this on
vintage PIII :-).
So I was able to resolve the issue by passing the /arch:SSE command line
parameter. Thanks!
On Wednesday, October 5, 2016 at 9:33:06 AM UTC-5, Adam Cozzette wrote:
>
> That's good to know that you're us
That's good to know that you're using protocol buffers on some vintage
hardware! :) I wonder if it's not the code per se that's being miscompiled
for the architecture but perhaps just the serialized descriptor data that's
being linked into the binary. It might be interesting to try saving the
descr
Sorry, I forgot to answer your question. Yes, it happens every time. But
only on Pentium 3 (!) machines.
On Tuesday, October 4, 2016 at 12:37:24 PM UTC-5, Adam Cozzette wrote:
>
> It sounds like the static descriptor data is somehow getting corrupted. On
> the affected systems does it happen rep
We now also know that this only happens on Windows 2003 x86 machines which
have a Pentium 3 processor. My first attempt to provide an executable with
optimization and SSE2 support disabled have been unsuccessful. At this
point I don't think it's something that's related to Protocol Buffers, it
It sounds like the static descriptor data is somehow getting corrupted. On
the affected systems does it happen reproducibly every time the application
starts up?
On Mon, Oct 3, 2016 at 10:54 AM, Ingmar Koecher
wrote:
> I can now also confirm that this problem only occurs on Windows Server
> 2003
I can now also confirm that this problem only occurs on Windows Server 2003
x86 hosts.
On Monday, October 3, 2016 at 8:48:48 AM UTC-5, Ingmar Koecher wrote:
>
> We've been using protocol buffers for a couple of months (version 2,
> exclusively on Windows) and while it works on 99.9% of systems,
