similar to: [LLVMdev] Adding encryption "pass" to back-end

LLVM IR represents higher level than assembler code, it keeps some names and it is easier to revert the IR to source code than a binary format. The main task of LLVM IR is code generation. I don't think adding obfuscation has particular worth, those who need it can use tools and approaches specifically aimed at obfuscation. Even simple rename of identifiers in source code makes C/C++ file

Hi ! Here is the situation. I created a pass in lib/Transforms/Obfuscation. I added a createFlattening() in IPO.h and in my code to be able to use it in PassManagerBuilder.cpp (lib/Transforms/IPO) in the method PopulateModulePassManager() so I can add my pass to standard passes. It all works if I add all my files in the lib/Transforms/IPO directory. But I want to keep them away in the

Hi ! I'm trying to modify the code in a machine function pass… I added a new basicblock and I want to add a jump to an another BB from my new BB. Here is my code : bool Obfuscation::runOnMachineFunction(MachineFunction &MF) { MachineBasicBlock *newEntry = MF.CreateMachineBasicBlock(); MF.insert(MF.begin(), newEntry); std::vector<MachineBasicBlock*> origBB;

Hello everybody! I am a Linux admin trying to move my mail system based on qmail to the software which is more spam-protected: exim4 + dovecot-1.0rc15 + pgsql . I've downloaded and rebuild dovecot from src.rpm (for fc4). During the testing stage I've discovered two troubles: 1) the problem with deliver (...I'm not sure it's a really bug). Here is relevant part of my

HI, I am interested in whether LLVM bit-code is ready for a distribution format(stored in software distribution package); is it easy to revert LLVM IR to C/C++ source code like Java byte code? My understanding is that. 1. LLVM IR is more like assembly code, so it is not easy for reverse engineering. 2. If it is easy for reverse engineering, does it mean it is not suitable for distribution

The next LLVM social in Paris will happen on January 30th, 2018. Everyone interested in LLVM, Clang, lldb, Polly, lld, ... is invited to join. Event details, including registration (free but mandatory) at http://www.meetup.com/LLVM-Clang-social For this meetup, Adrien Guinet, Serge Guelton and Juan Manuel Martinez will talk about the "Challenges when building an LLVM bitcode

On 8 Dec 1997, Stefan Nehlsen wrote: > Hello, > > is there anybody out there, who is working on NIS+ support for Samba? > > If not I will start with it: > > 1. Making "nis homedir (G)" work with NIS+. if you explain to me how it works, i will look at it. > 2. Mapping the smbpasswd file to a NIS+ table. (Does this really > make sense?) yes it does,

Hi everyone, I'm currently working on a project in which I would like to encrypt the output of LLVM's linker and add a piece of code to the executable, able to decrypt and execute it. I looked around the "post-link-opts" option of the linker, but since we're working on bytecode here, I was wondering if you guys had any experience with that. Any ideas/comments/advices

For some reasons the afs tokenforwarding stuff has changed siginificantly from v 2.9p2 to 2.9.9p2. This makes it impossible to use public key authenticication in a standart AFS environment. I don't know the reasons for these changes. In any case attached is a patch which restores the old behaviour. Regards Serge -- Serge Droz Paul Scherrer Institut mailto:serge.droz at

The PGO was my first guess but I can get a lot of information. At first, I follow the explanation at http://clang.llvm.org/docs/UsersManual.html#profiling-with-instrumentation but instead of llvm-profdata merge, I used llvm-profdata show *.profraw. Sadly, the information I get is the total number of function, the maximum function count and the maximum internal block count. Do you know if you

Yeah I have already see pintool but I need this to work with ARM and Intel. If I remember correctly, pintool does not work on ARM (or quite bad). My goal with the instrumentation is, once I have the information (time + call), to choose (during a second compilation) if some of my passes are applicable or not. Greetings, Johan On 17 Jul 2015, at 16:09, Kenneth Adam Miller <kennethadammiller

On Sat, Oct 14, 2017 at 10:58:17PM -0500, Kavon Farvardin via llvm-dev wrote: > > something simpler will do, IMHO. Happy to discuss this further if > > folks are in California next week :) > > Yes, I'll be in California next week, let's chat! > > We could make use of the autotuner I'm currently building: > > https://github.com/kavon/autotune > >

I see. Thanks for clarifying. I'm Ok with merging these if Dean agrees, as I believe he's the code owner. Thanks, Hans On Thu, Jan 26, 2017 at 11:47 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote: > There were no LLVM tests for presence of XRay instrumentation map in the > emitted assembly. You can see that https://reviews.llvm.org/D28624 adds this > check to the

Our 8-bit port for PIC16 has taken roughly about 18 months to get to where we are now. Our instruction set is not orthogonal, data memory is banked, program memory is paged, there is only one accumulator and two pointer registers, and the use of indirect memory access is really expensive. So we had to implement some non conventional approaches to get the model working. For the most part, LLVM

I'm wondering why the lit tests didn't catch this as part of testing rc1 on ARM. On Thu, Jan 26, 2017 at 11:25 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote: > XRay is tested automatically on build-bots with tests in LLVM and > compiler-rt . Or are you asking for manual testing instructions? > Of these 2 patches, the compiler-rt patch depends on LLVM patch because

How is XRay tested? IIRC, Renato didn't see any test failures on ARM? Merging sounds reasonbaly, I'd just like to understand what's the risk for the branch. On Thu, Jan 26, 2017 at 10:29 AM, Serge Rogatch <serge.rogatch at gmail.com> wrote: > Hans, these changes reached trunk in https://reviews.llvm.org/rL292516 and > https://reviews.llvm.org/rL292517 . Could you look?

Hi all, I'm new to LLVM dev mailling list and I'm starting to discover some aspects of LLVM. Actually I'm looking for a solution to create a tool chain for my own chip (a 8bit micro controller processor) that include a compiler/linker/assembler toolset and a simulator/debugger. >From what I've read, LLVM is a good tool to implement a compiler for this proprietary platform,

> On 15 May 2018 at 22:43 Gandalf Corvotempesta <gandalf.corvotempesta at gmail.com> wrote: > > > Hi to all > I was looking at protonmail.com > Is possible to implement and end-to-end encryption with dovecot, where > server-side there is no private key to decrypt messages? > You could probably automate this with sieve and e.g. GnuPG, which would mean that all your

Hi I personally use gpgit https://github.com/EtiennePerot/gpgit Which does the encryption of messages. Then I use a sieve script which calls gpgit for every msg and encrypts before saving into mailbox Cheers tobi Am 16.05.2018 um 10:24 schrieb Gandalf Corvotempesta: > Il giorno mer 16 mag 2018 alle ore 06:09 Aki Tuomi <aki.tuomi at dovecot.fi> > ha scritto: >> You could

Il giorno mer 16 mag 2018 alle ore 11:19 <tobisworld at gmail.com> ha scritto: > I personally use gpgit https://github.com/EtiennePerot/gpgit > Which does the encryption of messages. Then I use a sieve script which > calls gpgit for every msg and encrypts before saving into mailbox If I understood properly, for this to work, a public key must be stored on server, so that every