search for: sanest

...#39;ve overridden EmitGlobalVariable() from AsmPrinter >> because I didn't see any other spot to put this special directive. > Have you thought about always tagging such global variables with > __attribute__((section("fancyaddresspace"))) as well? That seems to be > the sanest way I can think of. Yes, but it seems a little odd to me. Is it correct to assume that different sections imply different address spaces ? I rather wanted to have a special asm directive on the top of section definitions to switch between memories following an identical section layout for both...

...At the moment, I've overridden EmitGlobalVariable() from AsmPrinter > because I didn't see any other spot to put this special directive. Have you thought about always tagging such global variables with __attribute__((section("fancyaddresspace"))) as well? That seems to be the sanest way I can think of. Joerg

...hould* be split between registers and stack. The relevant callbacks in clang only get to suggest one type (+ a padding dummy going before if they want); they can't (currently) say "put the first 4 bytes here and the rest there". Given that constraint "byval" is probably the sanest option since it's special anyway. That could be changed of course, but I'm not convinced Clang would be improved for it. Tim.

...guess the problem is not source-compatibility for > wine but binary-compatibility for CrossOver. In that case, I'd suggest > dlopen'ing and checking for the symbol you want. There's also issues with structure changes which won't be caught that way. libwmapro sounds like the sanest solution, short of doing the same thing with Wine.

...: > > One workaround is to use -mstackrealign where ever -msse2 is used > > Yes, that was one of the options mentioned in the article I linked > (http://www.peterstock.co.uk/games/mingw_sse) Can someone confirm that -mstackrealign fixes this issue? If it works, that seems like the sanest solution. Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

Ralph Giles wrote: >> With current settings, MSVS links debug version of flac.exe (and other >> .exe and .dll files) with the release version of libogg_static.lib. >> MSVS issues a "warning LNK4098: defaultlib 'libcmt.lib' conflicts with use >> of other libs; use /NODEFAULTLIB:library" > > Sounds like a bug. Debug targets should link to debug builds

Thanks for your quick response Joerg. We have a very small test case where there is global array and its address space attribute specified like in the following code const int __attribute__((address_space(256))) fangle[13] = {2341, 4681, 7022, 9362, 11703, 1403,16384, 18725, 21065, 23406, 25746, 28087, 30427}; I need to put its initializer in another memory because it has a different

...n EmitGlobalVariable() from AsmPrinter > >>because I didn't see any other spot to put this special directive. > >Have you thought about always tagging such global variables with > >__attribute__((section("fancyaddresspace"))) as well? That seems to be > >the sanest way I can think of. > > Yes, but it seems a little odd to me. Is it correct to assume that > different sections imply different address spaces ? > I rather wanted to have a special asm directive on the top of > section definitions to switch between memories following an > identic...

Hi Jean-Philippe, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2 next-20180221] [cannot apply to iommu/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Jean-Philippe-Brucker/Add-virtio-iommu-driver/20180217-075417

Hi Jean-Philippe, I love your patch! Yet something to improve: [auto build test ERROR on linus/master] [also build test ERROR on v4.16-rc2 next-20180221] [cannot apply to iommu/next] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux/commits/Jean-Philippe-Brucker/Add-virtio-iommu-driver/20180217-075417

At the moment, Syslinux doesn't support the 64bit feature of EXT4 (which is now set on by default). Considering the following code, I am wondering whether such support can be added to Syslinux. GRUB2 supports the 64bit feature of EXT4 since: 2012-07-02: Experimental support for 64-bit http://git.savannah.gnu.org/cgit/grub.git/commit/grub-core/fs/ext2.c?id=

...ssed above, but it would build. b) Actually make any IOMMU driver work as module. Whilst it would certainly be a nice feature, it's a bigger problem and I don't think it has its place in this series. c) Make VIRTIO_IOMMU depend on VIRTIO_MMIO=y instead of VIRTIO_MMIO, which I think is the sanest for now (and does work), even though distro kernels probably all have VIRTIO=m. I prefer doing c) now and experiment with b) once I got some time. Thanks, Jean

...looking bugzilla entries for it, but it still looks broken if I upgrade. Thanks for your response. I can confirm that this is indeed a Java problem. I followed your suggestion and downgroaded java-1.8.0-openjdk to version1.8.0.222.b10, and fonts rendered correctly. Now I wonder what would be the sanest way to solve this. As it looks, it's downgrading as described and then put this in /etc/yum.conf: exclude=java-1.8.0-openjdk* Correct me if I'm wrong. Niki -- Microlinux - Solutions informatiques durables 7, place de l'?glise - 30730 Montpezat Site : https://www.microlinux.fr Mail...

...ogg debugging is not possible with such build method anyway. > > (I know that such thing is very dangerous for C++ program that uses STL/Boost/etc. > But libogg is a pure C library, so it seems to be safe. A bit ugly though.) I'd be keen to have the windows build automatically do the sanest possible thing, preferably with anyone having to copy files. Cheers, Erik -- ---------------------------------------------------------------------- Erik de Castro Lopo http://www.mega-nerd.com/

On 2013-09-30 4:53 PM, Erik de Castro Lopo wrote: > I'd be keen to have the windows build automatically do the sanest possible thing, > preferably with anyone having to copy files. The way we've been doing the Opus stuff is to have the project files expect a build in a parallel checkout. so: c:\dev\flac\FLAC.sln expects to find an ogg build in c:\dev\ogg\win32\VS2010\ Not as obvious as having a monolithi...

...the fastest possible build performance." So /LTCG option was added too. And now Debug build uses libogg_static.lib from .\objs\debug\lib folder. (the dependency for both release and debug is objs\$(ConfigurationName)\lib\libogg_static.lib) (not "automatic", but currently "the sanest possible thing", IMHO) -------------- next part -------------- A non-text attachment was scrubbed... Name: vcproj.zip Type: application/zip Size: 2326 bytes Desc: not available Url : http://lists.xiph.org/pipermail/flac-dev/attachments/20131003/b7257516/attachment-0001.zip

On 03/09/15 03:59 PM, lvqcl wrote: > Tristan Matthews wrote: > >> >Unable to test on win32 at the moment, please give this a try. Feedback welcome. > > I wonder why misaligned stack is a problem only for the FLAC library. > There are many other libraries inside VLC... > > BTW: FLAC 1.3.1 uses -msse2 option by default. Do you remove it? > Otherwise libFLAC may crash

Hi Everyone, This question might be a long shot, but is it possible to mix and match com32 programs written against Syslinux 3 with com32 programs written against Syslinux 4 without recompiling. We are trying to have our com32 programs run with different versions of Syslinux without modification. Appreciate any advice, thanks in advance.

...nter bodyweight poultry pokes brandishes > poems ama mightiness assam countless actinolite merges crave technic > accomplishers bombast creation bonaparte savors portion menaced scroll > teethe thawing adumbrating icicle bergland memorized practise > acoustically explanatory sanest audrey humbler polyhedral exclaimer > memorization barnard sculpt hypocrisy mends estimation corrigible > pleasantness examination teared terminology exclusion boats alfred > scoops exegesis tensed telecommunicate bonus hotbed theirs tattooed > hot hotelman exposes horrid sc...

...address string in the form of "full address with quotes stripped from local part but otherwise not decoded" and nothing else throughout, which touches on quite a bit of code. It makes it indeterminate and not always possible to reassemble the original, it's a bit of a trainwreck. The sanest option to me seems to me to be to store a decoded local part and domain in addition to the detail in mail_recipient, and keeping a now properly rfc822 encoded address in sync with it. However, this would cause a deviation from existing behaviour for the full original user (the quotes would be seen)...