search for: _today_

...nd-line options. The problem I'm looking at is that the defaults for a lot of these things are based on target, which AFAICT is based on an out-of-date assumption about how target correlates to debugger. I'm proposing to package up known sets of stuff that we're having to contend with _today_ in a way that's easier to talk about and do something about than the target-oriented mish-mash we have now. It's a whole lot simpler to say something like "FreeBSD implies LLDB" instead of "FreeBSD implies accelerator tables and standard TLS opcode and no pubnames or pubtype...

...working on the GN build would have worked on the cmake build). However, this is true independently of where the GN build files are stored. - GN isn't a cmake replacement, for distro reasons and whatnot. I wholeheartedly agree with this. Maybe GN will become better here, but cmake is ubiquitous _today_, and it's backed by a company who's interested in keeping it around, so it will be around for a long time. I think this is cmake's biggest strength. That's why I'm not proposing on replacing the cmake build. If the GN build at some point is way better (compiler-rt, lldb, etc add...

Does anyone know how to make www.ud.com's Think Cancer Research Program Work under wine? I got it to install, but then it can't contact the server to register. Any ideas/suggestions? Thanks in advance, Dan W

Or, if this cannot be done easily, please, disable the "utf-8" value in source(..., ) function on Windows R. source(..., encoding = "utf-8") -> error: "utf-8" does not work right on Windows. -> (or, at least) warning: "utf-8" is handled by "best fit" on Windows and some characters in string literals may be automatically changed. Because, at

...ect. It is not their responsibility to read the documentation for you, and if you had read and understood it, you would not have used source(,encoding="UTF-8") with characters not representable in current native encoding on Windows. The authors should not be blamed for that the design _today_ does not seem perfect for _todays_ systems (and how could they have guessed at that time Windows will still not support UTF-8 as native encoding today). Tomas > Thanks, > Tomas > > > On Thu, Apr 11, 2019 at 8:53 AM Tom?? Bo?il <borilt at gmail.com> wrote: >> For me, th...

Hi I am working on deploying voip for my company and would like to seek some advice on the number of E1 lines we need to rent. Our telco told us that there can be at most 30 concurrent channels on an E1 line. Typically, what is the maximum number of DIDs that we can allocate to that E1 line before users get frequent "all lines are busy"? We are running a support center with mostly

...e time information is defined as a set of global variables > just the same as for the runtime definitions. The full use of > LLVM Types (especially derived types like structures and > pointers) can be used to define the global variables. If you just want to do this _today_ you already can. We have an "appending" linkage type which can make this very simple. Basically global arrays with appending linkage automatically merge together when bytecode files are linked (just like 'section' are merged in a traditional linker). If you want to implement yo...

...build). However, this is true independently of where > > the GN build files are stored. > > > > - GN isn't a cmake replacement, for distro reasons and whatnot. I > > wholeheartedly agree with this. Maybe GN will become better here, but > cmake > > is ubiquitous _today_, and it's backed by a company who's interested in > > keeping it around, so it will be around for a long time. I think this is > > cmake's biggest strength. That's why I'm not proposing on replacing the > > cmake build. If the GN build at some point is way bett...

...where >>> > the GN build files are stored. >>> > >>> > - GN isn't a cmake replacement, for distro reasons and whatnot. I >>> > wholeheartedly agree with this. Maybe GN will become better here, but >>> cmake >>> > is ubiquitous _today_, and it's backed by a company who's interested in >>> > keeping it around, so it will be around for a long time. I think this >>> is >>> > cmake's biggest strength. That's why I'm not proposing on replacing the >>> > cmake build. If t...

...ined as a set of global variables > > just the same as for the runtime definitions. The full use of > > LLVM Types (especially derived types like structures and > > pointers) can be used to define the global variables. > > If you just want to do this _today_ you already can. We have an > "appending" linkage type which can make this very simple. Basically > global arrays with appending linkage automatically merge together when > bytecode files are linked (just like 'section' are merged in a traditional > linker). If you...

On Sun, 2003-11-16 at 13:01, Vipin Gokhale wrote: > While on the subject of annotating bytecode with analysis info, could I > entice someone to also think about carrying other types of source-level > annotations through into bytecode ? This is particularly useful for > situations where one wants to use LLVM infrastructure for its > whole-program optimization capabilities,

Any easy way to do this as some kind of overlay, so they GN files wouldn't live in the LLVM repository, but in a separate one? (this might avoid some of the community discussion - though would perhaps still likely have the issue I see as most significant: With a sufficient number of developers using GN, the rate of build breaks due to those developers missing CMake file updates might rise to

Chris Lattner wrote: > On Sun, 16 Nov 2003, Reid Spencer wrote: > > >>On Sun, 2003-11-16 at 11:17, Chris Lattner wrote: >> >> >>>No, it's all or nothing. Once linked, they cannot be seperated (easily). >>>However, especially when using the JIT, there is little overhead for >>>running a gigantic program that only has 1% of the functions

I've been planning to build a dual Opteron server for awhile. I'd like to get people's suggestions on a suitable motherboard. I've looked at the Tyan K8SE (S2892) and K8SRE (S2891) but would like to find more Linux-specific experiences with these boards. Some features I expect are at least 4 SATA (SATA-300?) ports, serial console support in the BIOS, USB 2.0 and IEEE-1394

...by anyone using nbdkit to access VMware. - The Windows patches could be added _after_ we do the stable release so they have plenty of time to sit in development. At the moment I have to keep rebasing them. - (The not so good one) RHEL 8 demands that we either rebase nbdkit now, as in _today_, or else we will wait for many months before our customers can use the new features. Therefore I propose the two following patches. The first one removes the mention of list_exports and nbdkit*export* APIs from the 1.22 release notes. The second one is for stable-1.22 only (before 1.22.0 goes...

This is basically a reboot of the previous thread titled About the "debugger target" except that "target" was really too strong a term for what I had intended to use this feature for. "Debugger tuning" is more like it. You don't need to have read the previous thread, I'll recap here. Fundamentally, Clang/LLVM uses DWARF as the specification for the