search for: akira

*** BLURB HERE *** Bean Huo (5): fs/buffer: clean up block_commit_write fs/buffer.c: convert block_commit_write to return void ext4: No need to check return value of block_commit_write() fs/ocfs2: No need to check return value of block_commit_write() udf: No need to check return value of block_commit_write() fs/buffer.c | 24 +++++++-----------------

Hi, Product "AccountsService" was disappeared. https://bugs.freedesktop.org/enter_bug.cgi Only contact by gitlab ? Thanks, Akira Nakajima On 2018/11/20 16:19, Alan Coopersmith wrote: > On 11/19/18 10:50 PM, Nakajima Akira wrote: >> Hi, >> >> Mailing list of AccountsService does not found. >> https://lists.freedesktop.org/mailman/listinfo/ >> >> Only found gitlab which looks hardly wor...

I propose that we make Akira Hatanaka the code owner for the Mips code generator. He has worked on the Mips code generator for four years now and done high quality work that whole time. He is the key person inside of Mips for reviewing patches and giving advice to other developers regarding new Mips work. To assure the f...

...een having problems with logging in and password authentication. a. I can't seem to get it to compile MD5 support -- it only seems to support plain, plain-file, and pam. b. Whenever I try to log in, I always get something along the following lines in /var/log/messages .... Jan 16 17:52:15 akira imap-login: close(master) failed: Bad file descriptor Jan 16 17:55:33 akira imap-auth: Userinfo pam doesn't support DIGEST-MD5 method Jan 16 18:08:28 akira imap-master: Login process died too early - shutting down (I also included one about MD5 in there too! :-)) Basically, the imap-login pro...

...for these builtins. You are expecting them > to behave as if they were the standard library calls. They are not > equivalent and the naming similarity is an unfortunate historical artifact. > Use the standard library functions instead. > > -Jim > > On Apr 27, 2011, at 1:22 PM, Akira Hatanaka wrote: > > > I declared gi2 as "volatile" and I think gi2 is still incremented once. > > Here is a snippet of the code. Line 39 - 42 increments gi2. > > > > According to the standard, shouldn't ++gi2 be executed twice regardless > of whether gi2...

...SjLj exception > handling. Any other use, including any direct calls of the builtins in user > code, are a bad idea with no guaranteed behaviour. That they're exposed at > all is, again, for historical purposes. Don't use them. > > -Jim > > On Apr 27, 2011, at 3:45 PM, Akira Hatanaka wrote: > > > Okay. I understand builtin functions do not have to behave exactly the > same way as standard library functions. What I wanted to know is what should > the code generated by llvm (clang + llc) look like (I am working on the Mips > back-end now). I guess there...

On Mar 25, 2013, at 12:04 PM, Akira Hatanaka <ahatanak at gmail.com> wrote: > This patch adds parameter "EliminateFI" to RegScavenger::scavengeRegister, which tells register scavenger not to eliminate frame index of the emergency spill slot if set to false. > > I have pseudo load, store and copy instruction...

On Fri, Dec 5, 2014 at 2:40 PM, Eric Christopher <echristo at gmail.com> wrote: > > > On Wed Dec 03 2014 at 11:39:23 AM Akira Hatanaka <ahatanak at gmail.com> > wrote: > >> On Tue, Dec 2, 2014 at 4:38 PM, Eric Christopher <echristo at gmail.com> >> wrote: >> >>> >>> >>> On Tue Dec 02 2014 at 4:31:43 PM Akira Hatanaka <ahatanak at gmail.com> >>>...

...l compiler use in the context of SjLj exception handling. Any other use, including any direct calls of the builtins in user code, are a bad idea with no guaranteed behaviour. That they're exposed at all is, again, for historical purposes. Don't use them. -Jim On Apr 27, 2011, at 3:45 PM, Akira Hatanaka wrote: > Okay. I understand builtin functions do not have to behave exactly the same way as standard library functions. What I wanted to know is what should the code generated by llvm (clang + llc) look like (I am working on the Mips back-end now). I guess there should be a behavior us...

On Tue, Dec 2, 2014 at 4:38 PM, Eric Christopher <echristo at gmail.com> wrote: > > > On Tue Dec 02 2014 at 4:31:43 PM Akira Hatanaka <ahatanak at gmail.com> > wrote: > >> On Tue, Dec 2, 2014 at 3:21 PM, Eric Christopher <echristo at gmail.com> >> wrote: >> >>> On Mon Dec 01 2014 at 4:22:15 PM Bob Wilson <bob.wilson at apple.com> >>> wrote: >>> >>...

...at apple.com> wrote: > >> Thanks for your feedback, Eric. >> >> I still think we may be talking past each other a little bit, but rather >> than >> > > Might be, sorry if so :( > > >> delving further into the details right now, I’ve suggested to Akira that >> he look into how we should handle other kinds of options. I’m hoping that >> as we look at more of them, we will gain some insight into the approach >> that we want to take here. This patch really only deals with the easy >> cases, and whether we use Akira’s approach...

...email)? # line 39 - 47 ldr r1, LCPI1_1 ldr r2, [r1] add r2, r2, #1 str r2, [r1] add r4, pc, #8 @ eh_setjmp begin str r4, [r0, #4] mov r0, #0 add pc, pc, #0 mov r0, #1 @ eh_setjmp end ... LCPI1_1: .long _gi2 .align 2 On Wed, Apr 27, 2011 at 11:38 AM, Akira Hatanaka <ahatanak at gmail.com> wrote: > I have another basic question about setjmp/longjmp. > > When I compile and run the following program, is it expected that global > variable gi2 will be incremented twice? It seems that the code generated > with clang and llc increments...

Thanks for your feedback, Eric. I still think we may be talking past each other a little bit, but rather than delving further into the details right now, I’ve suggested to Akira that he look into how we should handle other kinds of options. I’m hoping that as we look at more of them, we will gain some insight into the approach that we want to take here. This patch really only deals with the easy cases, and whether we use Akira’s approach or not, I’m not especially worried...

Hi Akira, Just two very minor things that I missed the first time around. 1. The 'fixup" member of ELFRelocation entry should be "Fixup" instead. 2. Since we're always passing in a non-NULL fixup, that should probably be a reference, not a pointer. Good for commit with those tweaks....

> On Nov 19, 2014, at 4:52 PM, Eric Christopher <echristo at gmail.com> wrote: > > > > On Wed Nov 19 2014 at 4:39:42 PM Akira Hatanaka <ahatanak at gmail.com <mailto:ahatanak at gmail.com>> wrote: > On Wed, Nov 19, 2014 at 3:28 PM, Eric Christopher <echristo at gmail.com <mailto:echristo at gmail.com>> wrote: > So my general concern here is that lots of command line options that don't nee...

This patch adds parameter "EliminateFI" to RegScavenger::scavengeRegister, which tells register scavenger not to eliminate frame index of the emergency spill slot if set to false. I have pseudo load, store and copy instructions which are generated during register allocation and expanded post-RA but before the final stack size is known. I use register scavenger to search for a temporary

...machine code Mips Delay Slot Filler MachineDominator Tree Construction Machine Natural Loop Construction Mips Assembly Printer Delete Garbage Collector Information On Tue, Apr 24, 2012 at 11:36 PM, Anton Korobeynikov < anton at korobeynikov.info> wrote: > Hi Akira, > > > When I add -verify-machineinstrs, it complains that there are > instructions > > after terminator instructions. > Yes, -verify-machineinstrs and -verify-coalescing are your friends here :) > > -- > With best regards, Anton Korobeynikov > Faculty of Mathematic...

----- Original Message ----- > From: "Jakob Stoklund Olesen" <stoklund at 2pi.dk> > To: "Akira Hatanaka" <ahatanak at gmail.com> > Cc: "LLVM Developers Mailing List" <llvmdev at cs.uiuc.edu>, "Hal Finkel" <hfinkel at anl.gov> > Sent: Tuesday, March 26, 2013 12:40:44 PM > Subject: Re: [LLVMdev] [PATCH] RegScavenger::scavengeRegister > &g...

I have a question about MCExpr and its subclasses defined in MCExpr.h. I am trying to get Mips' direct object emission working. Line 283 of MCElfStreamer.cpp reads like this: 00283 case MCExpr::Target: llvm_unreachable("Can't handle target exprs yet!"); Does this mean that if I use a subclass of MCTargetExpr to lower MachineOperands to MCOperands, it won't work?

HI Akira, Please include the mailing list on replies. Using an MCExpr is the right way to build up things like symbol+offset. ARM has examples for that, as well, which may prove useful. For printing, the target libraries can do that however they want, including using the generic print method for expressi...