Now for char. The standard doesn't say which of those two interpretations should be correct.

(..........)

Some compilers offer a command-line switch to control which one it will be. Some compilers have different defaults depending on what OS they're running on, so they can match the OS convention.

In most code, it really shouldn't matter. They are treated as three distinct types, for the purposes of overloading. Pointers to one of those types aren't compatible with pointers to another type. Type calling strlen with a signed char* or an unsigned char*; it won't work.

Use signed char when you want a one-byte signed numeric type, and use unsigned char when you want an one-byte unsigned numeric type. Use plain old char when you want to hold characters.

(..........)

It's more correct to say that it's compiler-specific and you should not count on char being signed or unsigned when using char without a signed or unsigned qualifier.

Otherwise you would face the following problem: you write and debug the program assuming that char is signed by default and then it is recompiled with a compiler assuming otherwise and the program behaviour changes drastically. If you rely on this assumption only once in a while in your code you risk facing unintended behaviour in some cases which are only triggered in your program under specific conditions and are very hard to detect and debug.

On a related note, we made the "default signedness of char varies" problem go away by feeding the compiler -funsigned-char. This gives us consistent behavior on all platforms, and defaults to 8-bit clean text processing (which gets us halfway to UTF-8 support).

(<remote>: mean remote branch on this git repository, just like the branch "orign" to "git clone" or the branch "git-svn" to "git svn", just cvsimport doesn't do it for you. "cvs" or "git-cvs" is good)(what if there are new branch on cvs server?)

Incremental Imports/Update repository to the latestIn root directory of git repository and on master branch. With above git config,

なら1 〔…だとすれば〕そういう話なら引き受けましょうIf that is the case, I will do it.他言しないなら話してやろうI will tell you on condition that you keep it to yourself.2 〔…に関して言えば〕山なら富士が一番だWhen it comes to mountains, Fuji is supreme.彼女は花ならばらというところだIf I were to compare her to a flower, it would be to a rose.田中ならいません(You want) Tanaka? He's out.その件なら人事課に行ってくれGo to the personnel section about that.私なら異存はないAs for me, I have no objection.3 〔それなら〕なら，なぜあの時そう言わなかったのだIf so [Then], why didn't you say so at the time?

ついていく【付いて行く】I1 〔後に〕follow子供が母親の後からちょこちょこ付いて行ったThe child toddled along after his mother.2 〔一緒に〕go [come] withあなたに付いて行きたいI'd like to go [come] with you.娘の卒業式には妻が付いて行くことになっていますMy wife is going to accompany our daughter to her graduation ceremony.

すすめる【進める】1 〔前進させる〕将軍は兵を国境まで進めた「The general led the army [The general's troops advanced] to the frontier.彼は (将棋の) 歩を進めたHe moved the pawn forward.車をこの線まで進めて下さいMove the car up to this line.2 〔進展させる〕彼は交渉を進めたHe proceeded [went ahead] with the negotiations.この計画を進めてくださいPlease go on [ahead] with this plan.／Please carry this program forward.新工法は工事を進めるのに役立ったThe new technique in engineering served to speed up the construction work.この縁談を進めていいねThen it's all right to 「act on [go ahead with／proceed with] this suggestion for a match?3 〔昇進させる〕功績により彼は位一級を進められたOn account of his distinguished service, he was promoted one grade in rank.4 〔食欲を盛んにする〕この調味料は食欲を進めるThis seasoning stimulates the appetite.5 〔時刻を早くする〕時計を5分進めたI set the clock five minutes early.／I put [moved] the clock forward [ahead] by five minutes.6 〔程度を高める〕もう一歩進めて考えてみなさいGo a step further in your thinking.

いちどに【一度に】〔同時に〕at once, at a time, at the same time, simultaneously; 〔一挙に〕at 「a stretch [one sitting]; 〔皆いっしょに〕all together一度に二つの事に集中することはできないYou can't concentrate on two things at a time.みんな一度に入ろうとしては駄目だDon't try to get in all together.一度にどっと疲れが出た「All at once [Suddenly] I felt exhausted.

せめる【攻める】attack; assault; make an attack [assault]((on)); ((文)) assail敵を攻めるattack the enemy激しく攻めて要塞を占領するtake [win] a fortress by assault

やぶる 【敗る】

* （動ラ下二） * o 補足説明「やぶる（破）」と同源

やぶる 【破】

* 暦注の十二直の一。訴訟談判・家屋の取り壊しなどに吉、約束相談に凶という日。

やぶる【敗る】defeat; beat強敵を敗ったHe defeated [beat] a powerful rival.

つぶす【×潰す】I1 〔押し付けて形を崩す〕crush; smashぶどうをつぶしてぶどう酒を作るcrush grapes and make wineじゃがいもをつぶすmash potatoes2 〔金属製品をとかす〕⇒いつぶす(鋳潰す)3 〔畜殺する〕にわとりをつぶしてスープにしたI killed a chicken and made soup with it.4 〔埋めふさぐ〕穴をつぶすfill up a holeII1 〔体面・名誉を傷付ける〕彼女は父親の顔をつぶしたShe made her father lose face.／She embarrassed [shamed] her father.2 〔空いた時間を費やす，空費する〕暇をつぶすkill time定年後の父はぶらぶらして時間をつぶしているMy father is simply idling away his time since retirement.3 〔財産などを失う，破産させる〕彼は身代をつぶしたHe wasted [squandered] his fortune.彼は計画的に会社をつぶしたHe bankrupted his company deliberately.4 〔駄目にする，役に立たなくする〕大声を出し過ぎて声をつぶしてしまったI shouted so much that I 「lost my voice [went hoarse].経済の混乱がわずか1年間に3人の首相をつぶしたThe financial chaos brought down three prime ministers in a single year.

まえ【前】1 〔顔の向いている方〕前に進むproceed／go forwardそれは目の前にあるIt is right in front of you.まっすぐ前を見なさいLook straight ahead [before you].前の車に衝突したHe ran into the car ahead of him.前にならえStand at arm's length!2 〔面前〕人の前で恥をかかされたI was disgraced 「in front of people [in public].子供の前でそんな話はよしなさいDon't talk about things like that in front of the children.3 〔正面〕家の前の通りthe street in front of the house恥ずかしくて彼女の顔を前から見られなかったI was too shy to look her full in the face.4 〔物の先の方〕前から5番目の席the fifth seat from the front前の車両the front cars行列の前の方に立つstand near the head of a line5 〔ある事柄と対した時の状況〕折角の親切も厳格な規則の前では役に立たなかったHer kindness was of no use in the face of the strict rules.6 〔今より以前〕前の校長the former principal前の授業には出席しなかったI didn't attend the last class.その子は前に会った時より随分大きくなっているThe child has grown a lot since I saw him last.彼には前に会ったと思うI think I met him before.3年前に家を建てたI built my house three years ago.前にはここに銀行があったThere used to be a bank here.彼のことは前から聞いているI have often heard of him.7 〔ある時より以前〕戦争の始まる2年前でしたIt was two years before the war broke out.10月3日より前に返事をくださいPlease reply before [no later than] October 3.前の晩に読んだ本を彼に貸したI lent him the book I had read 「the night before [the previous night].1時5分前ですIt's five (minutes) to [((米))of] one.30前の女a woman who is not thirty yet／a woman under [on the right side of] thirty8 〔順序の先の方〕前のページにon the previous page前からの約束がありますI have a previous engagement.山田氏の前の知事はだれでしたかWho was the governor prior to Mr. Yamada?前の半分the first half前の例は後のよりよいThe former example is better than the latter.

おもしろい【面白い】1 〔楽しい，興味をそそられる〕interesting; 〔人を楽しませる〕amusingこのごろ勉強が面白いRecently I've come to enjoy my studies.会社の仕事は面白くないMy work at the office isn't interesting [any fun].会は面白かったですかDid you enjoy the meeting?ああ面白かった〔何かが終わって〕That was fun.魚が面白いように釣れたThe fish were biting like crazy.あれはなかなか面白い男だHe's a very interesting fellow.／〔ちょっと変わっていて〕He's quite a character.2 〔こっけいな〕funnyせりふが面白い芝居だThe dialogue of the play is witty.このまんがは面白くなかったThis cartoon wasn't funny.3 〔「面白くない」の形で，望ましくない〕どうも病状が面白くないThe patient isn't doing very well.

のこらず【残らず】all⇒ぜんぶ(全部)知っていることは残らずお話ししましたI have told you all I know.彼らは一人残らず不適格だと分かったThey proved unqualified 「to a man [to the last man].卵は一つ残らず腐っていたEvery single egg was addled.大きなステーキを残らず平らげたHe ate up every bite [scrap] of the big steak.

ぶんどり 【分捕り】

* ぶんどること。特に戦場で、敵の武器などを奪い取ること。 * o 「予算の—合戦」 o 「—品」

ともなう【伴う】1 〔付随する〕登山は多くの危険を伴うMountain climbing involves many risks.その事業には大きな困難が伴った((文)) The undertaking was attended with much difficulty.雨はひどい風を伴ったThe rain was accompanied by a high wind.権利には責任が伴うRights and responsibilities go hand in hand.少子化に伴って大学志願者が減ったWith the drop of the birthrate, the number of college applicants has decreased.2 〔連れて行く〕彼は秘書を伴って出掛けたHe went out accompanied by his secretary.学生を伴って博物館へ行ったI went to the museum with my students.彼は旅行にはいつも妻を伴って行くHe always takes his wife with him on his trips.3 〔釣り合いがとれる〕彼は収入に伴わない趣味の持ち主だったHe pursued hobbies that were out of keeping with his income.

いさむ【勇む】【例文】彼らは勇んで闘技場に入って来たThey came into the arena in high spirits.馬があんなに勇んでいるLook at that horse prancing along!

By editing .git/config you can setup unlimited amount of locations ofwhere to pull from and where to push to (and you can pull from manylocations to a same branch and push one branch to many locations)

VIVT cache has the following issues:- issue #1; two processes may use the same virtual address for differentphysical addresses, but will share the same cache line and see memorycorruption if no precaution is taken;

- issue #2; two processes may use different virtual addresses for thesame physical address (shared mapping), but will use different cachelines, causing all sorts of incoherence if no precaution is taken;

- issue #3; the same process may use different virtual addresses for thesame physical address (same shared mapping mapped several time in thesame process virtual memory), basically almost the same issue as issue #2.

The Linux kernel, solves issue #1 and #2 by flushing the cache at everycontext switch, and issue #3 by remapping the multiply mapped sharedmapping in "uncacheable, buffered only" mode if write buffer issufficiently well behaved, or "uncacheable, unbuffered" mode if writebuffer is buggy.

Now, if we look at VIPT, aliasing caches:- the physical tagging solves issue #1 automatically,- the cache colouring technique used in arch_get_unmapped_area solvesissue #2 and #3 by ensuring that the areas using the same physicaladdress will end up using the same cache lines, and avoid aliases "byconstruction".

VIPT non-aliasing caches have none of the three issues.

(.....................)

ARMv7 has non-aliasing VIPT D-cache

(.....................)

the I-cache on ARMv7 is an aliasing VIPT

(.....................)

Flushing the L1 cache has to use the virtual address even on PIPTcaches. In the Linux case, you can't use the kernel linear mapping toinvalidate an I-cache line if the intention is to use the code in userspace with a different virtual address.