search for: symbolises

Hi all, I am trying to add XRay support to the IR produced by GHC. Getting the basics working is not too complicated after adding the right function attribute but any analysis shows the function names but not the locations of the functions. In particular, I run a program which has been instrumented as follows: XRAY_OPTIONS="patch_premain=true xray_mode=xray-basic verbosity=1" ./llvm

> On 3 Dec 2018, at 23:01, Matthew Pickering via llvm-dev <llvm-dev at lists.llvm.org> wrote: > > Is anyone able to help me with this or suggest where I might be able > to get help? You’ve asked the right place, apologies for the delay I’m supposed to be answering these questions. > > Matt > On Mon, Nov 26, 2018 at 3:02 PM Matthew Pickering > <matthewtpickering

Hi David, Sorry for taking a few days to reply. It's not easy for you to compile a Haskell file to see the problem as the debug information is still WIP. Below I prove the IR for a simple hello world program which you can feed into llc. https://gist.github.com/05296933e37e87533a51d493b46aa48d The `out.ir` file can be passed straight to `llc`. Can you see anything obviously wrong? Matt

...nt to match. The numbers are: ###### 00 ###### 20 ###### 30 ###### 40 ###### 15 ###### 35 ###### 12 ###### 44 Right now I've solved it by doing this: exten => _######[0234]0,1,HangUp exten => _######[13]5,1,HangUp exten => ######12,1,HangUp exten => ######44,1,HangUp The ###### symbolises a fixed number, it's just censored away (and not important anyway) I was just wondering if there was a more intelligent approach, so this could be combined into one extension. Best regards, Mickey Binder

...---------- The following is the ACL information on a file. user::rwx group::--- #effective:--- group:readgroup:r-x #effective:r-x group:writegroup:rwx #effective:rwx mask:rwx other:--- Standard Unix permissions on this file appear as -rwx------+ (the + symbolises that the file has ACLs set) The following is the resulting file permissions and ACLs on an AFFECTED FILE. user::r-x user:username:rwx #effective:rwx group::r-x #effective:r-x group:writegroup:rwx #effective:rwx mask:rwx other:--- -r-xr-x---+ Whats Been Tr...

...----------------- The following is the ACL information on a file. user::rwx group::--- #effective:--- group:readgroup:r-x #effective:r-x group:writegroup:rwx #effective:rwx mask:rwx other:--- Standard Unix permissions on this file appear as -rwx------+ (the + symbolises that the file has ACLs set) The following is the resulting file permissions and ACLs on an AFFECTED FILE. user::r-x user:username:rwx #effective:rwx group::r-x #effective:r-x group:writegroup:rwx #effective:rwx mask:rwx other:--- -r-xr-x---+ Whats Been Tried ---...

I don't think NDEBUG is that easy. We use assert liberally[1] in templated code in headers. What about cast<>, which has assert(isa<...>...)? On ELF, you have an ODR problem, and you'll get either one or the other based on the whims of the dynamic linker. You could probably get things to the point that it sort of works, but I don't think we could support it without

...code and later analyse what they did. We tried and keep on trying the reverse way :) BTW, for the record, Matroska is a simplified version of matrioshka (or MATP?WKA in russian), the original name of the russian dolls. The idea comes from me and Frank Klemm gave us the name in russian. It just symbolises the fact that, like IFF formats, Matroska contains other Matroska elements. > haven't released or produced anything yet. This is the grown-up > equivalent of declaring 'I didn't get to do it my way, so I'm taking > my toys home with me' and watching to see which kids...

...code and later analyse what they did. We tried and keep on trying the reverse way :) BTW, for the record, Matroska is a simplified version of matrioshka (or MATP?WKA in russian), the original name of the russian dolls. The idea comes from me and Frank Klemm gave us the name in russian. It just symbolises the fact that, like IFF formats, Matroska contains other Matroska elements. > haven't released or produced anything yet. This is the grown-up > equivalent of declaring 'I didn't get to do it my way, so I'm taking > my toys home with me' and watching to see which kids...

With the recent thread on using C++11 in LLVM/clang, one of the recurring themes was a desire to make the internal headers more consumable. While I don't personally want any kind of stability guarantee for internal headers, I do think we can do more to ensure that any given snapshot of the headers is consumable from different compilers and build configurations. In practice this means

Please allow me to announce the creation of a new open source Media Container Format, named 'matroska' Project page is here http://sf.net/projects/matroska ; homepage is http://matroska.sourceforge.net , HTML should be online soon. Steve 'robux4' LHomme and myself have left the MCF project because of incompatibilities of our work with the project goals defined by the founder of

Please allow me to announce the creation of a new open source Media Container Format, named 'matroska' Project page is here http://sf.net/projects/matroska ; homepage is http://matroska.sourceforge.net , HTML should be online soon. Steve 'robux4' LHomme and myself have left the MCF project because of incompatibilities of our work with the project goals defined by the founder of