A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2006-April/063546.html below:

[Python-Dev] Who understands _ssl.c on Windows?

[Python-Dev] Who understands _ssl.c on Windows? [Python-Dev] Who understands _ssl.c on Windows?Georg Brandl g.brandl at gmx.net
Sat Apr 8 10:26:59 CEST 2006
Michael Hudson wrote:
> "Tim Peters" <tim.peters at gmail.com> writes:
> 
>> _Perhaps_ it's the case that doubles are aligned to an 8-byte boundary
>> when socketmodule.c is compiled, but (for some unknown reason) only to
>> a 4-byte boundary when _ssl.c is compiled.  Although that seems to
>> match the details in the bug report, I have no theory for how that
>> could happen (I don't see any MS packing pragmas anywhere).
> 
> Well, poking a bit reveals that _ssl and _socket are built by quite
> different mechanisms: _socket by a .vcproj but _ssl by "_ssl.mak".  I
> don't see anything overly suspicious in _ssl.mak, but I don't really
> know much about Windows compiler options...

A mailing list post found via Google suggests that Visual Studio automatically
sets the struct member alignment to 4 bytes when building via old .mak files,
for compatibility with older VC++.

Anyway, a /Zp8 flag should correct this.

Georg

More information about the Python-Dev mailing list

RetroSearch is an open source project built by @garambo | Open a GitHub Issue

Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo

HTML: 3.2 | Encoding: UTF-8 | Version: 0.7.4