similar to: [LLVMdev] suspicious typo in MCObjectDisassembler.cpp

Displaying 20 results from an estimated 200 matches similar to: "[LLVMdev] suspicious typo in MCObjectDisassembler.cpp"

2014 Jul 31
2
[LLVMdev] suspicious typo in MCObjectDisassembler.cpp
Any chance of adding some missing test coverage here? That code was dead (& evidently untested) before... On Thu, Jul 31, 2014 at 11:37 AM, Eric Christopher <echristo at gmail.com> wrote: > I believe you are correct. Fixed thusly: > > dzur:~/sources/llvm> git svn dcommit > Committing to https://llvm.org/svn/llvm-project/llvm/trunk ... > M
2014 Jul 31
2
[LLVMdev] Removing lib/MC/MCObjectDisassembler (and more?)
Oops sorry. lib/MC/MCAnalysis/MCObjectDisassembler.CPP Thanks. -eric On Jul 31, 2014 1:21 PM, "Kevin Enderby" <enderby at apple.com> wrote: > Eric, what file are your referring to? The path > lib/MC/MCObjectDisassembler does not end in a .cpp or .h and is not a > directory . > > Just a bit more info and I can get back to you if I’m using what your > asking
2014 Jul 31
6
[LLVMdev] Removing lib/MC/MCObjectDisassembler (and more?)
Seems to be largely untested... anyone using this? (cc'ing Kevin as he's the most likely candidate). At the least for MCAnalysis this appears to be unused, any ideas on what else can be deleted? I'll remove just this file unless there are objections tomorrow (or earlier if I get an ack from Kevin about it). -eric
2016 Jan 15
2
Is MCRelocationInfo::createExprForRelocation used out of tree?
Deleting LGTM. It is a leftover of MCAnalysis. Cheers, Rafael On 14 January 2016 at 16:54, Pete Cooper <peter_cooper at apple.com> wrote: > Hi Jim, Rafael > > As respective code owner and frequent committer to MC, any thoughts on this? > > Cheers, > Pete >> On Jan 12, 2016, at 1:07 PM, Pete Cooper <peter_cooper at apple.com> wrote: >> >> Hi all
2016 Jun 24
7
Representing MIPS ABI information in the triple as ARM/X86 do for EABI/EABIHF/X32
Hi, Having recently enabled IAS by default for the MIPS O32 ABI, I'm now trying to do the same thing for the MIPS N64 ABI. Unfortunately, it is not currently possible to enable IAS by default for the N64 ABI without also enabling it for the N32 ABI because this information is not reflected in the triple and that's the only information MipsMCAsmInfo has. This would be fine if it N32 was
2016 Jul 05
2
Representing MIPS ABI information in the triple as ARM/X86 do for EABI/EABIHF/X32
Hi Eric, It's the unsolved problems on the pass-MCTargetOptions-everywhere path that are my main concern with that approach rather than the amount of work. The first problem is that the result of IRObjectFile::CollectAsmUndefinedRefs() depends on the ABI but IRObjectFile doesn't know it. How would you deliver the ABI to IRObjectFile? The second problem is that IRLinker will link
2016 Jan 12
2
Is MCRelocationInfo::createExprForRelocation used out of tree?
Hi all The virtual method MCRelocationInfo::createExprForRelocation doesn’t appear to have any callers. Is anyone using it out of tree? In tree, its overridden in X86ELFRelocationInfo.cpp and X86MachORelocationInfo.cpp, but those overrides have 0% coverage (http://llvm.org/reports/coverage/lib/Target/X86/MCTargetDesc/X86MachORelocationInfo.cpp.gcov.html) I’d like to delete these methods and
2015 Apr 23
2
[LLVMdev] Get precise line/column debug info from LLVM IR
I am trying to locate instructions in an LLVM Pass by line and column number (reported by an third-party tool) to instrument them. To achieve this, I am compiling my source files with `clang -g -O0 -emit-llvm` and looking for the information in the metadata using this code: const DebugLoc &location = instruction->getDebugLoc(); // location.getLine() // location.getCol()
2013 Jul 09
0
[LLVMdev] Basic instructions for LLVM and Control Flow graph extraction
This isn't by itself too difficult, as I have done something similar recently, but does require some modifications of LLVM. The basic algorithm is simple: For each ISA instruction, create a new MachineInstr and add it to the current MachineBasicBlock. At each branch instruction, add it to the current MBB and add it to a list and create a new MBB. After creating your list of MBB, iterate
2013 Jul 09
2
[LLVMdev] Basic instructions for LLVM and Control Flow graph extraction
I am currently attempting to learn how to use LLVM for control flow graph extraction on linux (Ubuntu). Basically, I need to be able to break down specific basic functions blocks from assembly code, and use it to make a CFG. Do any of you upstanding human beings have any knowledge or resources that could possibly assist me in this task? I apologize if this is a very basic question. I have already
2001 Apr 10
1
Suspicious shadow listen port
# netstat -an | grep LISTEN tcp4 0 0 *.32785 *.* LISTEN tcp4 0 0 130.238.4.133.22 *.* LISTEN What in ?@# is 32785 ?? # lsof ... sshd 11152 root 5u IPv4 0x7003ded8 0t0 TCP *:32785 (LISTEN) sshd 11152 root 6u IPv4 0x7004ded8 0t0 TCP xxx.yyy.zzz.hhh:22 (LISTEN) ... #cat /etc/sshd_config Port 22
2014 Feb 13
0
[PATCH] efi: Suspicious size reduction in emalloc
From: Sylvain Gault <sylvain.gault at gmail.com> It could happen on 32 bits architecture that the memory size really allocated could be less than required. On 64 bits, allocate_pages may be called more times than needed. This closes bug #39. Signed-off-by: Sylvain Gault <sylvain.gault at gmail.com> --- efi/main.c | 4 +--- 1 file changed, 1 insertion(+), 3 deletions(-) diff --git
2007 Aug 13
1
[LLVMdev] Suspicious code for X86 target
Hi, I found some suspicious code in X86TargetLowering::getRegClassForInlineAsmConstraint, but I don't know if it's a bug or my poor understanding of what the code does. This is the code in question: (lib/Target/X86/X86ISelLowering.cpp:5064) if (VT == MVT::i32) return make_vector<unsigned>(X86::EAX, X86::EDX, X86::ECX, X86::EBX, 0); else if (VT == MVT::i16) return
2009 Sep 13
1
[LLVMdev] I am suspicious on the setting of _WIN32_WINNT
That's because when I am using Mingw to compile llvm. It's report can't find the API DWORD WINAPI GetProcessId( __in HANDLE Process ); In Mingw it's defined as #if (_WIN32_WINNT >= 0x0501) WINBASEAPI DWORD WINAPI GetProcessId(HANDLE); #endif but IN Wnidows SDK, there is nothing around GetProcessId. But from MSDN GetProcessId Function Retrieves the process identifier of
2010 Aug 08
1
[LLVMdev] Suspicious code in backend scheduler
Hello, Still trying to write a custom scheduler, I stumbled accross a highly suspicious code in all schedulers. In both ScheduleDAGFast.cpp and ScheduleDAGRRList.cpp, one can find this piece of code: SUnit *CopyFromSU = CreateNewSUnit(NULL); and then in the same files: SUnit *CreateNewSUnit(SDNode *N) { [...] SUnit *NewNode = NewSUnit(N); And finally in ScheduleDAGSDNodes.cpp: SUnit
2006 Aug 03
1
Suspicious sshd log messages in my syslog
Hello All, I'm using OpenSSH 4.3p2. I'm getting few messages in my syslog and it is shown below, Aug 02 11:15:19 foo sshd[4381]: Received window adjust for non-open channel 0. I found that sshd received a SSH_MSG_CHANNEL_WINDOW_ADJUST and it executes the function channel_input_window_adjust() in channels.c. I like to know how this can happen for a non-open channel. Is anything
2017 Dec 19
3
detect suspicious logins
does anyone know of a linux module (maybe similar to fail2ban) that could be installed which would monitor email logs (sign ins) and alert the user to any suspicious activity on their account? i suspect it would need to log geo location, device type and ip address to a database. it seems like a module like this would be very useful and should exist already? thanks in advance
2017 Dec 21
0
detect suspicious logins
Matthew Broadhead <matthew.broadhead at nbmlaw.co.uk> wrote: >> does anyone know of a linux module (maybe similar to fail2ban) that >> could be installed which would monitor email logs (sign ins) and alert >> the user to any suspicious activity on their account? I just monitor straight from the logs using homebrew utilties. @lbutlr" <kremels at kreme.com>
2017 Dec 20
0
detect suspicious logins
On Tue, 19 Dec 2017 17:13:10 +0000 Matthew Broadhead <matthew.broadhead at nbmlaw.co.uk> wrote: > does anyone know of a linux module (maybe similar to fail2ban) that > could be installed which would monitor email logs (sign ins) and > alert the user to any suspicious activity on their account? i > suspect it would need to log geo location, device type and ip address > to a
2017 Mar 07
0
Suspicious code in net_socket.c
On Mon, Mar 06, 2017 at 01:00:45PM +0300, Roman S wrote: > Module - net_socket.c > Function - get_known_addresses > --------------------------------------------------- > struct addrinfo *nai = xzalloc(sizeof *nai); > if(ai) > ai->ai_next = nai; > ai = nai; > -------------------------------------------------- > For my opinion, possible causes: > 1. Lost