-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 On 09/02/11 02:48, Richard Guenther wrote: > > Note that with all this mess I'll re-iterate some of my initial > thoughts. 1) why not do this C++ (or C) specific stuff in the > frontends, maybe at gimplifying/genericization time? That way you > wouldn't need to worry about middle-end features but you could rely > solely on what C/C++ permit. It is, after all, C++ _frontend_ > semantics that we enforce here, in the middle-end, which looks > out-of-place. Well, it's worth keeping in mind that fixing the way we handle bitfields is just one piece of a larger project. Furthermore, many of the ideas in the C++ memory model are applicable to other languages.
However, I must admit, I'm somewhat at a loss, I thought we were doing all this in stor-layout.c at the time we layout the structure's memory form then just trying to keep the code generator and optimizers from mucking things up by combining accesses and the like. Clearly I'm going to need to sit down and review the code as well. Which means learning about a part of GCC I've largely been able to ignore... Sigh... jeff -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iQEcBAEBAgAGBQJOYT2jAAoJEBRtltQi2kC7BF4IAJWwqzsPUdhsHaodlUfm1LRu JpMojs04wPVfu12+8zcXaWfitjOhEPJDPcZ5c0AHb74NRPJINJmjDvSBZWfFazaE CrZE/U9IBz7Ay8s/gw//uMIWDS8lNjjYFxpqn6VMUpY2F/4QSkDZtaTlsTfm8YfU +IZnwq82Johh8MzGDRuYY0HBKRdAotGS2F+SycdOxBGW6hnW0WR/2pt0BpIxNYgl ro0dOgSptWoEmOFzhlN9pVsFvImSjXVlbV9GnF4AsDrh9x9FIaFIpvhgZMUU8wc+ Akg2jgLy2hhysQ9JtES0rL9qrptPPcQVqCL8ct/sLB85vYw7oUxwSenj7w8mwmE= =yjMx -----END PGP SIGNATURE-----
